Jordan K. Hubbard wrote:
The matter should now rest since it's hard enough just enforcing your actual project name much less going after derivatives. What next? Someone could register any one of macosports.com, macosxports.com, macsoftwareports.com, etc etc (all of which are closer to macports and even more likely to cause confusion) and the project would quickly find itself spending more time chasing people with sticks than actually maintaining ports. The darwinports.com horse is already dead and buried, and the set of folks who still remember it as "darwinports" is a decreasing number of people, so at some point the problem will ultimately solve itself.
The usual reason to why it reappears is because the port view at e.g. foo.darwinports.com usually comes up higher in search results from e.g. Google than what the corresponding page in http://db.macports.org or http://macports.org/ports.php does...
And since it shows the same Portfile with the same version, people tend to get confused between darwinports and macports still. If the two (!) MacPorts lists could be consolidated (like the Guide has been), that would probably help clear things up ?
--anders _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
