Till Biedermann [2006-01-15 19:49]:
most of you might have noticed that I made a frontend to the mysql-based portsdatabase on crux.nu availible in the wiki:
Yes, I have been using the new for quite some time :D Didn't notice it wasn't finished :o
So please try it out and give some feedback on usability, improvement-suggestions, missing features and so on.
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 :) 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. Regarding the register procedure: s/CLC member/CRUX developer/g :)
1.) How should the application procedure for the portdb look like?
The simple solution is we allow only repos which take part in the new contrib. So the quality of ports and active maintenance guaranteed.
The other way is that every repo can be listed in the db. In this case should there be a registration form (like it is now with the old db) or is it better to use the mailing list (like we do for everything)?
Users might not want to .sync all of their ports they publish via httpup (like me :P). So I'd say keep it the way it is + enhancements for contrib.
2.) The other question is how to handle .sync-tagged (i.e. contrib-) ports in the origin repository? The old db lists the port both in contrib and in the httpup repo (which falsifies the duplicate stats btw.). I think it is better to exclude contrib ports from the origin httpup repo in the db listing. What do you think?
I agree. See also above for some more comments on that. Nice work :) Regards, Tilman -- GnuPG key available at http://code-monkey.de/files/tsauerbeck-public-key.asc