Jay Dolan wrote:
Lookin good :) I take it you plan to implement viewing the port (Pkgfile, .footprint, etc..) soon?
I construe this as a feature request. So here it is: http://crux.nu/cgi-bin/trac.cgi/wiki/PortDBportinfo?repository=core&port=firefox Displaying .footprint and .md5sum inline is not so important imho. I think the anchors for these files are enough. Other opinions?
... I think it is better to exclude contrib ports from the origin httpup repo in the db listing. What do you think?
Yea, I like that - each port only shows up once. *Or* you could show them in the original httpup, too, perhaps with some visual cue, indicating that it's also available in contrib. :)
I have chosen the way of complete exclusion. But the count of contributed ports is listed in the overview for each repository: http://crux.nu/cgi-bin/trac.cgi/wiki/PortDBrepoinfo?repository=jaeger Tilman Sauerbeck wrote:
The heading used in the "Duplicates" view is the same as the one used in the "Search" view. Slightly irritating.
The dupe-detection thing is a nice feature :)
Looks like you reviewed the old db :-) But anyhow the dupe-detection _is_ a nice feature. So here it is: http://crux.nu/cgi-bin/trac.cgi/wiki/PortDBstats#Duplicates
Did you consider removing ports that are in contrib and *one* other user repository only? In that case, the database could check whether it's that user repo the port is synced to contrib from, and not report a dupe in that case.
Like mentioned above, I exclude all (.sync)tagged ports from normal httpup repositories. This is a clean and easy to implement way of solving this problem. Last but not least some (final) words to the application procedure. I suggest the following: Participation in the contrib is _not_ required, so every repo can be listed in the PortsDB. When a maintainer wants to have his repo listed, he has to announce it on the official mailing list and ask for inclusion in the db. So everybody can have a look at the new repo and if something is not ok, it can be discussed there. When there are no objections arising after a period of 3-5 days the repo will be added to the db. Any comments on that? (silence will be assumed as agreement :-)) Regards Till -- http://www.tbmnet.de ___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de