Henne Vogelsang <hvogel@opensuse.org> writes:

Im sorry but you are (still) designing the OBS for packagemanagers instead of people :)

Nice polemics. I agree the package manager has some potential to catch up a bit, but I also agree with Adrian that using agregates for this kind of stuff is a crutch until the package manager really supports recursively adding in base repos. I think a 'common repository' is just a way to implement something different: As a user, I want to rely on reccomendations, I want to have one place that I go to and that I use to do the base install and to then look for packages to add or update as I need them. This can be implemented by flattening out such a selection (aggregate) but it could also be implemented by a 'search path', a search DAG, actually, and the package manager does the flattening dynamically. To the user it doesn't make a difference, but to the web service provider it means significant savings in storage and bandwidth. I was always under the impression that the package manager heads towards this dynamic capability or am I mistaken? S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org