[RFC] A change to the way packages are built

[Michal Hrusecky]

David Lang - 10:41  5.05.16 wrote:
> On Thu, 5 May 2016, Michal Hrusecky wrote:
> 
> > 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 :-)
> 
> can it do cross-compiles?

Should be able to, we used to use it at some point, but don't know any details.
In openSUSE we first switched to qemu-user builds (to avoid all the troubles
with cross-compilation) and later on to native workers (to speed up things).
But OpenWRT/LEDE can do it on it's own and I wouldn't suggest throwing out
current build system.