| |||||||||||||
Upgrading?Upgrading?Posted Jun 28, 2004 16:05 UTC (Mon) by rfunk (subscriber, #4054)Parent article: A look at Slackware 10.0
I started with Slackware back in 1995, switched to Red Hat 3.03 because
(Log in to post comments)
Upgrading? Posted Jun 28, 2004 16:59 UTC (Mon) by otavio (subscriber, #337) [Link] If you look in release announce you will see some new tools in contrib directory to help on this.Now, upgrade a slack installation *should* be easy. Try it and see yourself ;-)
Upgrading? Posted Jun 28, 2004 20:26 UTC (Mon) by DaveK (subscriber, #2531) [Link] Upgrading Slackware distributions is easy.ihave migrated several systems over time from 8.1->9.0->9.1 and then via current to 10.0. I use the swaret tool which appeared in the /extras directory, but now seems to have gone away again, which includes a system of dependencies. Alternatively, one can download the various packages and invoke upgradepkg from the standard slackware package tools. Most new slackware packages are also careful not to clobber configuration files and instead deposit a .new file slongside. the install script then discards the .new files if the md5sums match, leaving the administrator to reconcile any differences.
Regarding "Dependency Hell" Posted Jun 28, 2004 20:51 UTC (Mon) by dowdle (subscriber, #659) [Link] Just to clarify, dependency hell doesn't really exist anymore. It wasfirst cured when Red Hat introduced Red Hat Network and the up2date application which was a trial / subscription service. Then people created apt for rpm and yum. These days, with Fedora Core, yum and up2date are basically interchangable. Setting up a yum repository takes about a minute if you already have a web accessible directory with the desired packages in it. Of course RHEL customers are using the up2date system with RHN. Much of dependency hell was caused by bad packagers but not all.
|
|||||||||||||