I started working on some changes for Magus to parse the MOVED file. In MidnightBSD, a lot of tools don't do much with that file so it's never been consistently managed.Â The idea is that we can index it with each magus run and then provide the data in the index file generated for packages.Â This would provide hints about packages that were really removed vs renamed.Â We could then install the renamed/moved package on upgrades and when using the mport list command, it could more accurately guess if packages were removed or just unavailable.Â This solves a problem that's bugged me for awhile with mport.Â Of course, we're only working on the first step now.Â Â The steps for this are: 1. add it to the magus indexer.Â (needs testing) 2. Export the data during a magus bless from the new MOVED table in the postgresql database to a table in the generated sqlite index files for mport to use.Â (need to update magus bless utility) 3. Modify mport package manager to read the data from the table in the indexÂ 4. Update the mport list command to display more accurate data about packages that have expired, will expire, or are deleted/removed 5. Modify the mport info command to display information about package expiry etcÂ 6. Modify the upgrade command (and possibly update) to make more intelligent decisions about package renames and possibly ask a question on upgrade/update/install paths about packages that are deprecated.