On Nov 11, 2003, Axel Thimm <Axel.Thimm@xxxxxxxxxxxxxxxxxxx> wrote: >> The idea (as I understand it) is that people want to easily have >> add-on packages in their system without a risk that this might modify >> core components. > E.g. choose their stability level. So let's use stability criterions. It's not really the same. One of the points is at the time of reporting a bug. Say I find a bug in Mozilla, or in mplayer. Unless I can pinpoint which repository I got Mozilla from, or the exact dependency of mplayer that caused the bug, to figure out where I should report it, I'll be at a loss. Being able to make sure that a certain package (along with all of its dependencies) is part of the Core makes it simpler to assert whether a bug is in the Core or not, as long as you stick to only Extras repositories. As soon as you introduce Alternatives, any hopes of easily identifying the source of a problem are gone, and this doesn't even get into inter-repository compatibility problems. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer
