[RFC] A change to the way packages are built
Michal Hrusecky
Michal.Hrusecky at nic.cz
Thu May 5 01:16:34 PDT 2016
David Lang - 18:20 4.05.16 wrote:
> Debian has ...
Just for the sake of discussion and inspiration, how openSUSE does it's rolling
release. We have OBS, which is server software, connected to multiple builders.
It has projects and in those projects packages. Packages can have sources
somewhere in the git and git hook can trigger rebuild. Builds are done in new
cleanly installed environment (there is option to have some precached) which is
afterward thrown away. When package is built, all packages in the project that
depends on it are rebuild, unless there is no change to the package - it is
binary same as the last one (somebody fixed coding style?).
When package is send to Tumbleweed (rolling distro) it has to first build in
the project it is submitted from, then it is put into staging project where it
is built against clean Tumbleweed and packages depending on it from Tumbleweed
are rebuild. Once done, staging project is run through automatic test and if
it passes, it is merged.
One more side note, OBS is opensource, it can build packages for multiple
architectures and distributions (openSUSE, SUSE, RHEL, Debian, ...) and they
accept patches to support more distributions :-)
More information about the Lede-dev
mailing list