On Thu, 16 Oct 2003 09:28:15 +0200 "Daniel K. Gebhart" <dkg@con-fuse.org> wrote: Hi Daniel,
What do you mean by 'availability'? Would the script only check for availability of source() files, or try to build the port?
It just makes sure, that there will be no 404 error. It will not try to build the ports.
got it. It's clear now.
In both cases, I'd prefer not to add another tag to Pkgfile, I suggest an (independent) external list or something similar. Or, better again, the script could periodically check all ports and submit problems to the maintainers who want to be contacted, and eventually publish a html report somewhere.
This was also my second idea. I think it would be better in this way and so I'll do it.
I'll add a third one (just to make thinks more complicated): if the script is developed as a tool mainly for maintainers, it could handle a filter param (ie: maintainer name or port path). This way a maintainer could be easily check only his/her ports. ie: # scriptname --maintainer=sip@varlock.com would check my ports; or: # scriptname --path=/usr/ports/custom Just an idea. Regards, Simone