Linux.com

a package mismanager

Posted by: Anonymous Coward on March 08, 2007 06:12 PM
it's not *manager* in the first place, at most package *advisor* since it doesn't have (overridable but) power to control what it must take care of -- dependencies.

when you're localhost type with only a single system to care of, it might suffice; when you have at least a dozen, you have to grow up and dump slackwarish approach.

seen that quite a few times, and was kind of smart enough not to buy that myself.

--
Michael Shigorin

#

Return to Conary: An innovative second-generation package manager