Citando Scott Haneda : > > Unfortunately, no, in my research, that is not the case. One of the > very best things that could be done, would be for MacPorts to have > every maintainer of every port contact the developer of that > software, and ask for al link. > > I have done this for every port I worked on. When I finish the ASSP > port, there will be a link. I did the memtester port, ( > http://pyropus.ca/software/memtester/ ) and went to him to get a > link. > > I will be finishing the pureftpd port, and will also get the same > linking. What anchor text we suggest to use should be talked about, > I am not sure that "MacPorts" is the best. It would be a discussion > worth having for sure. >
The anchor is one thing, the destination is another. Which is the page to link from upstream webpage? I see at least 3 possibilities: 1) www.macports.org: that's what I did for mpd. There is also a text explaining the command to install mpd from macports. 2) http://www.macports.org/ports.php and if possible the specific page for the port. But it is not informative in any way and you cannot get a link for some ports (mpd for example) 3) http://trac.macports.org/browser/trunk/dports/audio/mpd/Portfile None of those is both informative on the port and readable. Note that fink has beautiful pages for each port: http://pdb.finkproject.org/pdb/package.php/mpd. mpd_darwinports_com also has a page (not more interesting than the Portfile). So who will write a Portfile_to_webpage script to have a readable and informative page for each port? In a perfect world, this page would also feature a link to the bugs reported against this port. Doing better than http://packages.debian.org/sid/mpd could be a goal. Regards, Emmanuel
signature.asc
Description: Digital signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
