On Jan 20, 2008, at 3:16 AM, Jordan K. Hubbard wrote:

1. Easy enough - just change the Portfile with "port edit <portname>", make your changes, test/edit/repeat.

2. The submit process, however, should be a lot easier than it is.  Today, you open a new trac ticket and attach your new Portfile asking "can somebody please commit this for me?"   In a more ideal world, there would be a "port submit" command which caused far more magical things to happen.

Whatever happened to the "port submit" project initiative anyway?  Wasn't that supposed to come about for free with the remote index? :-)


Sure, it was! Remote Index would have brought that and many other goodies. Sadly enough, remote index was never implemented, so we don't have them at present :-( Hope somebody steps up in the not too distant future to start doing some of the leg work ;-)

So, as an alternative, our guidelines to submitting tickets are very well explained in this document: http://guide.macports.org/#project.tickets (regardless of the port having a maintainer or not).

Regards,...


-jmpp



- Jordan

On Jan 19, 2008, at 6:18 PM, kevin brown wrote:


Dev,

Suppose I wanted to upgrade a version of a port with no maintainer,say, http://www.macports.org/ports.php?by=name&substr=pixen, from version 2.2 to 3.0.  How might I go about making the change on my local box (leaving the submitting a patch process out for the time being)?  Is there a doc you could point me to?  I'm familiar with how to perform this task in gentoo, but not yet very familiar with macports. 

- Kevin
 _______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev