ports-mgmt/portmaster distfile expression matching

jhell jhell at DataIX.net
Sat Jan 16 06:43:25 UTC 2010

On Fri, 15 Jan 2010 22:23, wxs@ wrote:
> On Fri, Jan 15, 2010 at 09:32:32PM -0500, jhell wrote:
>> Hi Doug,
>> Recently in upgrading x11-wm/xmonad and x11-wm/xmonad-contrib I had
>> noticed that when portmaster asks to delete a distfile, when it asks about
>> xmonad-0.9.1 it was also asking to delete the xmonad-contrib-0.9.1 before
>> it had even upgraded xmonad-contrib. Is this a problem on portmasters
>> behalf or is this on ports structure side ?.
>> What do you or anyone else think about each port possibly keeping
>> obsolete-distfiles list one much like distinfo but a concatenated list of
>> previous distinfo's that had once been used allowing a ( make distclean )
>> or something routine to be built into the ports infrastructure to parse
>> that file in each port ?
> Bad idea. That list will get quite large for some ports.
> I believe there is a PR about embedding the distinfo information into

That would be keen!

As for the idea I had, I was thinking more along the lines of pruning the 
proposed obsolete-dists file to only have the versions for the last three 
or so releases in there but ultimately would be up to the port maintainer 
to judge whether something should stay or not.

If the distinfo is recorded into the +CONTENTS file, how is the removing 
program going to differentiate between say 3 other versions that the user 
may have choose not to remove in a previous instance. ? or for that, the 
problem that I had "xmonad-0.9.1 -> xmonad-contrib-0.9.1" where it wanted 
to remove anything that had a xmonad prefix.

I think a simple obsolete file would be a better way around this as you 
could write into the ports system a way to parse the number of lines that 
are in the current distinfo file and multiply that by 2 or 3 or what ever 
a maintainer would choose by given variable in their own port and 
ultimately re-write the obsolete file list.

Just my thoughts but written lists are usually more of a sure practice 
rather than trying to match every pattern that J Random Developer decides 
to give to their tar-balls.

Best regards,



More information about the freebsd-ports mailing list