On 02/06/05 19:50 Johannes Winkelmann wrote:
Just an idea: what about looking at the REPO file instead?
I don't think this is a good idea, since it places an additional burden on the developers (regenerate the repo even if there's no need for it). Given that I'd like to have as many people as possible taking part in this new contrib, I'd like to not introduce any additional complexity over maintaining a personal repo (besides the duplicates, of course).
Well, if the private repo contains a fair number of ports I think that usual updates would keep the repo alive without the need of unnecessary refreshes. I recognise this could be annoying if one has few ports in his repo.
Other than that, I think I got slighly missunderstood, or maybe I didn't understand Jay's script: as far as I understood, even if the port is not in the input set anymore, the 'unmaintained' tag is only set after a certain time. It's not about measuring a maintainer's activity, it's just about marking those ports which have been dropped by a maintainer as 'unmaintained'. This cannot be seen by looking at the REPO file, since a REPO file of an active maintainer will never be older than a month; he might nevertheless drop ports. Please let me know if I'm not clear here.
preprep [1] handles this by maintaining a list if ports which were synced last time, and synced this time; those is $last but not in $this are those which have to be marked 'unmaintained'.
As Jay replies in this thread, the missing ports will simply not be part of the new contrib anymore. I prefer this solution, that encourages the presence only of maintained ports in private collections: I'm not much in favour of providing an additional 'unmaintained' collection (or subset of ports). This is another reason for which I suggested checking the contributed repsitories as a whole, I like the fact that a contributor would submit the ports in the spirit "Here's a set of ports that I currently use and maintain". Maybe I'm too afraid the new contrib will become a large pile of junk :) Of course, others opinion may be different. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com