Originally posted by SlackwareInAZ
Or to put it another way, if I was to reinstall 10.1 and update to current, whether using swaret, slackpkg, slapt-get, etc, or by manually uninstalling and reinstalling all the current packages Pat has changed without upgrading aaa, then how can this be identical to 10.2 (assuming that no more changes occur before 10.2 is released).
If you do a fresh full install of 10.1, and update to current (or 10.2, there identical RIGHT NOW) without upgrading aaa* there will be a few differences between a fresh install of 10.2:
1) This is something I forgot. Since you are not upgrading aaa_base, you will need to change /etc/slackware-version to 10.2.0
# echo "Slackware 10.2.0" > /etc/slackware-version
If you did upgrade the aaa*, there is no issue, either, because this was a fresh install and no other updates were made to the libraries included in aaa*. This is only the case sometimes, specifically, wehn stuff is still clean (no other updated libraries.
Easier to use a solution that ALWAYS works (don't upgrade aaa*), than one that sometimes works.
2) You will have additional unsupported packages (e.g. GNOME)
3) You will be missing new packages (e.g. Subversion, cyrus-sasl (maybe not, since this may be picked up by swaret --dep), etc.)
Some ideas on ways to update:
1) Track current, skip aaa* packages. Note that this is not recomended if you are not able to handle an occasionally whacky system.
2) Fresh install of 10.2. Back up important configs, data, etc. Note that this is easier for some (like those who have sane partitioning schemes) than others. Also note that you will need to re-install any non-Slackware packages.
On a side note, this can be a GOOD thing. Get in the habit of making build scripts for packages you need that Slackware doesn't provide. You can re-build the packages on you new system using only backed-up scripts. This can avoid a lot of issues. You may see breakage on stuff from third parties (e.g. LinuxPackages) due to libraries changing or missing deps. You never have this issue building stuff on your own.
3) Follow UPGRADE.TXT. If there are any issues with that, you will see that others will have the same issues, and a resolution will usually be issued fairly quickly.
Some things I think are a not so good idea:
1) You want to install 10.2 fresh. You don't have the install CDs yet, so you install 10.1 fresh and upgrade to 10.2.
This is sub-optimal for a few reasons.
a) 10.2 is available via BitTorrent. Why subject the FTP servers to all the extra abuse.
b) You have to read the changelog to see what needs to be added/removed.
c) It is a much harder way to get 10.2, since you will be editing a lot of *.new config files.
d) When you have an issue (say with ALSA, for example), you will have more work to solve your issue. Is it an Alsa configuration issue? Is it an issue with your upgrade method? Is it an issue with your kernel configuration? Less things to worry about if you just do a fresh install of 10.2.
More on upgrading packages like aaa* (and the *solibs for that matter). If in doubt about what a package will do, unpack (explodepkg, or, my favorite, tar -xvzf)a copy of the package in /tmp and see what it installs. Then, check out what is on your system already. Is it redundant? Is it downgrading libraries?