On Thu, Oct 25, Klaus Kaempf wrote:
The current way of development is
- trunk for everything - branches for product maintenance
and your example shows that this is not sufficient.
What you (and probably others too, I wonder why noone else speaks up) need is a 'dedicated bugfix branch' not influenced by ongoing development in other areas.
In other words: More branches.
If you don't want/need to follow the development in one branch then you can use use e.g. the devel package, or leave your local copy at a certain revision. I guess the 'UI guys'n'girls' would prefer to not being in need to compile the sublibs at all. sat-solver e.g. is just a build time requirement. If a libzypp-devel package was used, you won't see it at all. Things might be easyer if - instead of checkig out a certain SVN revision - one could simply order the -devel package based on revision "XYZ". Sort of internal -devel package build service, shiping the packages including header files and libs (incl. the *.so.*), prepared to be installed in /usr/local. get-devel-pkg libzypp [-r7623] -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org