limiting installed (re)versions in port?

[Jeremy Lavergne]

> One aspect of MacPorts that concerns me (compared to fink) is that  
> it seems possible with port to accumulate
> a huge number of installed (but deactivated) package (re)versions  
> over time. I can understand the concept of
> keeping some of the most recent (re)versions but not every single  
> one. It would make much more sense to adopt
> the approach where only those previous (re)versions would be kept up  
> to some user defined limit (perhaps defaulting to 2 or 3 previous  
> (re)versions of the same package). When a new (re)version of the  
> same package is installed  and the limit of archived (re)versions  
> has been meet, the oldest copy would be purged from the system.  
> Otherwise the numbers of deactivated ports will bloat the system  
> over time. Has a ticket ever been opened for such a feature in port?

`port upgrade -u ...` somewhat covers that functionality in that it  
will remove the old version prior to activating the new one.

You can remove specific versions using the fully qualified name (port  
uninstall NAME @...[+VARIANTS]), which is available through `port  
installed [...]`

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4024 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20091101/2c05ce30/attachment.bin>