[Buildroot] Multiple versions of packages
luca at lucaceresoli.net
Mon Aug 11 12:21:50 UTC 2014
Jordi Llonch wrote:
> For a particular use case, I need to build different minor versions for
> the same package.
> The most notable example is mainly for interpreted languages: PHP,
> 5.5.x, 5.4.x, 5.3.x, ruby, etc. also for mysql or other packages where
> state can be incompatible across versions.
> I have implemented packages like "php53" and "php54" in a BR2_EXTERNAL.
> I am looking for better approaches on how to do this.
> Any thoughts or ideas?
Only one version of package is generally supported in Buildroot.
Supporting more versions involves a maintenance burden that is worth
only for a few packages.
For very critical packages (kernel, bootloaders, toolchain components),
there is a version selector in the package config options. See for
example Bootloaders -> Barebox version.
This is the most complete but also the most complex way of supporting
different versions. PHP and Ruby are surely not critical enough to be in
For some other packages (qt/qt5, python/python3) we have different
packages for the different versions, which is basically what you do
This is less complex but may lead to some duplicated code and once again
it increases the amount of maintenance work, so it is generally not done
unless tha package is an important part of a system infrastructure.
I can't say whether PHP or Ruby might deserve this status. If you feel
they do and are willing to bring this in mainline Buildroot, feel free
to open the discussion with your motivations for considering the
package so important and why one version cannot meet all needs.
Another possibility is to select a different version for a specific
build. Just type
to build with a specific version of <PKG>. This is a more limited
approach as it does not allow to easily handle the case where
different versions of the package need different build instructions.
Yet another possibility is to maintain one branch for each combination
of package versions that you need to maintain. Of course this won't end
in mainline Buildroot, but it's OK to do on your local versioning system
if you want.
Hope this helps.
More information about the buildroot