> Christian A Str�mmen [Number1/NumeroUno] <[EMAIL PROTECTED]> writes:

> > What's up with Mandrake???   Why is EVERYTHING added to cooker and not to
> > normal updates?  The use of MandrakeUpdate seems to be quite unnecessary
> > since Mandrake doesn't add stuff to it..  Everything seems to be in
> > development updates and for glibc 2.2.


> We can't do everything.

> Currently we chose to not put resources into doing that sort of stuff.

*nod*   yes, i can see that backporting everything to play nicely with older 
versions of LM would be a living nightmare.  I enjoy the cookers rapid 
induction and patching of new software, and I wouldnt want the Mandrake 
developers quagmired in other jobs.  

I personally use the cooker myself - even on semi-production machines (moms 
comp and such,  heh)  My only gripe here is that the cooker can be difficult 
at times.   Look at the recent problems with 'kernel too old' from installing 
the recent glibc2 package.  The BM and new lib policies have also kept me on 
my toes.  Id imagine it would be hard to make _every_ package in the cooker 
be in sync with each other - and be safe to install on any machine.  Id 
personally recommend the cooker to everyone - if not for the very small 
chance that they could install something in some order that totally hoses 
their machine.

I would greatly love to see a cooker advisories web page.  Lists of recent 
cooker updates, lists of obsolete and 'outstanding' packages (where the 
package or its dependencies are not up to date with the rest of the system - 
an example would be the glibc 2.2 packages before the locales stuff was 
brought up to speed), a simple cooker forum, a freshmeat-like changelog of 
new packages, and whatever else works.  Another nice idea would be to have a 
searchable 'rpm -q' database, so people could get information about packages 
and files on a perfectly normal cooker machine.  Next time you try to install 
a package, and it says libf00baz.so.1.4-3 is needed,  you could enter that 
into the web page and ask it what rpm it belongs to.  (it sorta doesnt work 
if you _dont_ have the package already installed - im sure many people are 
going to hit me over the head with rpm -qf)  

Your thoughts?

Jason

Reply via email to