Downgraded packages with Slack upgrade
I had discussed this in a previous thread, but I don't remember coming to any resolution so I thought I'd try again to figure something out. I'm going to be upgrading my Slack version again, and I'd like to avoid the biggest annoyance with my past upgrade: when going through and upgrading every package (as part of UPGRADE.TXT), every package gets replaced, even those with a higher version number. For example, I keep gaim up to date, but the upgrade will downgrade the new version to whatever package is in the new version of Slack. Is there a way to directly avoid this, or, if not, at least a way to see a list of which existing packages were replaced with new ones so I can manually go through and check for downgrades?
Along the same lines, is there a list of newly installed packages, so I can see things like firefox/thunderbird packages being installed when I already have them on my system, duplicate packages being installed for checkinstall packages I already have but for whatever reason didn't get named right, etc.? What does everyone else to do avoid these issues? |
Quote:
Add your initials to packages you create Use SWareT to upgrade Pay attention when my initials pop up Same goes for third party stuff. They should have initials in the package name. If they don't, add them before installing. Quote:
Quote:
|
You can avoid such problems by:
|
Thanks for the advice all.
Quote:
|
|
All times are GMT -5. The time now is 12:41 PM. |