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
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? :-) - 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
On Jan 20, 2008, at 01:46, Jordan K. Hubbard wrote:
On Jan 19, 2008, at 6:18 PM, kevin brown wrote:
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.
1. Easy enough - just change the Portfile with "port edit <portname>", make your changes, test/edit/repeat.
[snip] The doc to refer you to is: http://guide.macports.org/ If you find it's unclear or doesn't contain the information you need, please point out how it could be improved. The guide authors are still refining it and would probably appreciate feedback.
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
On Jan 21, 2008, at 6:15 AM, Juan Manuel Palacios wrote:
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 ;-)
It was implemented, just never integrated ;) All the sources are in subversion, though probably suffering from bit-rot at this point. - Kevin
On Jan 21, 2008, at 2:25 PM, Kevin Van Vechten wrote:
On Jan 21, 2008, at 6:15 AM, Juan Manuel Palacios wrote:
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 ;-)
It was implemented, just never integrated ;) All the sources are in subversion, though probably suffering from bit-rot at this point.
Note that the some of this stuff is manifested in mpwa (look at http://db.macports.org ), which uses a (heavilly) modified version of Kevin's submit code to submit changes to the db. A cron job runs every 20 minutes (and has been for about 10 months now) to autosubmit any ports that have been changed and checked into svn. In a better world, any joe blow could simply run "port submit" to submit changes to a port. That almost (maybe does?) work right now. So mpwa can serve as the index, but we don't have any integration currently to query that index. Allowing generalized submission to mpwa would require a stronger implementation of user authentication and signing, which isn't too hard. Anyone interested should review the docs http://svn.macports.org/repository/macports/users/jberry/mpwa/doc/. I'd be happy to brainstorm, take criticism, answer questions, etc. The one thing I don't have right now, however, is the time to take this further just now (though I hope to in the indefinite and optimistic future). Others are welcome to pick this up, with appropriate discussion of course. James
participants (6)
-
James Berry
-
Jordan K. Hubbard
-
Juan Manuel Palacios
-
kevin brown
-
Kevin Van Vechten
-
Ryan Schmidt