I am happy that there finally is a discussion on this topic.
One thing we have to account for is if we branch the ports tree for B1 and
then only cherry pick from master, how are people going to update to B2 (or
R1) when it is released.
On Feb 26, 2016 6:19 PM, "Ingo Weinhold" <ingo_weinhold@xxxxxx> wrote:
On 26.02.2016 11:36, Michael Lotz wrote:
Right now the build master setup only builds packages from new/changed
recipes. This can easily be changed to "build new/changed recipes and
everything that depends on them" which would ensure that a new version
of a dependency doesn't break the other recipes (updates to autotools
come to mind). I've implemented the necessary logic already and it
shouldn't change much on the master side. It will be a lot more taxing
for the builders though as a lot more recipes will be built when common
dependencies change.
While building an affected package's dependencies might be a good idea (to
see if anything breaks), we probably want to avoid replacing those packages
in the repository, if not actually necessary. From a user's POV it would
certainly be suboptimal, if a large amount of packages would need to be
updated frequently. Versioning would be a problem as well -- we can't
replace a package with one that has the same version.
CU, Ingo
