On Wed, Jul 31, 2013 at 03:15:46PM +0200, Bernhard Voelker wrote:
On 07/31/2013 02:01 PM, Klaus Kaempf wrote:
If some change in Factory breaks the build, I want to see it in _my_ (devel) project.
+1
... and even more: when I build may package in Base:System, it would be nice to have it also (tried to) built against a bleeding edge tool chain. If that fails, I wold be able to react long before that tool's bleeding egde version goes into Base:Build and Factory.
It does not sounds cool to create staging projects for each of 100+ devel projects we do use. What would be worthwhile is to be aware that your package does not build in Factory staging project. From my POW he biggest design flaw in OBS is that is project centric. It is nice and easy to create your own project. But it's impossible for a package maintainer to have any clue what's going around with his package. And we are mostly selfish beasts, so we do take a care about our own stuff. Atm all you can do is to go through a number of random projects, like devel project, factory, various staging** subprojects made by coolo. Simply switch a focus from projects* to package and you'll see how easy it will be package/ devel - OK factory - OK staging-gcc48 - FAIL staging-rpm - FAIL staging-libpng15 - OK * I do consider the idea of devel projects as the most harmfull thing we have to deal with. It is build on the similar ideas like "components", but that seems to be proven it does not work. Interdependencies are real and kill-ya. ** I **do not** rant against staging projects, they are the right way how to have "master" releasable and develop features in topic branches. Regards Michal Vyskocil
That means on the other hand that the packages required for building (like GCC, make, autotools, coreutils, etc.) provide such bleeding edge versions as early as possible. Sounds fair enough.
Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org