This time James Sparenberg <[EMAIL PROTECTED]> becomes daring and writes:
> As urpmi exists.... I wouldn't think it would work. I've seen the > distro upgrade done on debian.. If you aren't too far out of date it > works .... eventually. But if you are way out of date it has a real > chance of creating an unusable box. One other diff I believe exists (as > it's been explained to me) apt-get grabs .... installs... grabs... using > less ram and less disk. URPMI grabs and grabs then installs. For a > really large installation size this could be a problem. I've done the release-to-cooker thing a few times...it works, for the most part...as long as you keep cooker *and* contrib in your sources. Q&A moves packages between main and contrib some times, and if you have a package that used to be on main installed, and it's moved to contrib without you having it in your sources, you'll bang your head into a wall. But if you keep cooker and contrib (at least...I also keep plf) in your sources, I don't see the problem...at least I've never had a problem :) One thing you *will* have to deal with by hand (and it's where debian is ahead where it comes to dist-upgrade) is those packages that change their config files format...if you have a package that uses a new config type, the new config sample will be an .rpmnew file and the program will refuse to work until you fix the config you have. Happened to me with either openssh or proftpd once :) Outside of that...never had a complaint, as long as you keep a generous amount of space in your /var (10gig partition in my desktop :) Vox -- Think of the Linux community as a niche economy isolated by its beliefs. Kind of like the Amish, except that our religion requires us to use _higher_ technology than everyone else. -- Donald B. Marti Jr.
pgp00000.pgp
Description: PGP signature
