Boost 1.34 has been officially released. What needs to be done to move this into the macport system?
On Jun 4, 2007, at 11:01, Sancho McCann wrote:
Boost 1.34 has been officially released. What needs to be done to move this into the macport system?
Looks like the boost port has no maintainer, as you perhaps already discovered. That means it's up for adoption! Would you be interested in maintaining it, or at least submitting a patch to update it to 1.34?
Yeah, I could do it. It would be my first maintenance task ever on a port though, so I would need some guidance. Is there a good reference to read to explain what I'd need to do? Sancho On 4-Jun-07, at 1:18 PM, Ryan Schmidt wrote:
On Jun 4, 2007, at 11:01, Sancho McCann wrote:
Boost 1.34 has been officially released. What needs to be done to move this into the macport system?
Looks like the boost port has no maintainer, as you perhaps already discovered. That means it's up for adoption! Would you be interested in maintaining it, or at least submitting a patch to update it to 1.34?
On Jun 4, 2007, at 15:49, Sancho McCann wrote:
On 4-Jun-07, at 1:18 PM, Ryan Schmidt wrote:
On Jun 4, 2007, at 11:01, Sancho McCann wrote:
Boost 1.34 has been officially released. What needs to be done to move this into the macport system?
Looks like the boost port has no maintainer, as you perhaps already discovered. That means it's up for adoption! Would you be interested in maintaining it, or at least submitting a patch to update it to 1.34?
Yeah, I could do it. It would be my first maintenance task ever on a port though, so I would need some guidance. Is there a good reference to read to explain what I'd need to do?
Not exactly, unfortunately. The documentation from when the project was called DarwinPorts has not been migrated to MacPorts yet, and is out of date. But you can still read it here in the Internet Archive: http://web.archive.org/web/20060427120406/darwinports.opendarwin.org/ docs/ The best advice is to look at existing portfiles and see how they do things. You will want to make a copy of the boost portfile: $ cd `port dir boost` $ cp Portfile Portfile.orig Then edit the portfile: $ port edit boost Then make your changes and try installing the port. Once you have a change you're happy with and want to share, get a diff of your changes: $ diff Portfile.orig Portfile > Portfile.diff Attach the diff to a new ticket in MacPorts' Trac installation. Then write back to the list and tell us the ticket number and someone will look at it and commit it.
Ryan Schmidt <ryandesign@macports.org> on Monday, June 4, 2007 at 2:23 PM -0800 wrote:
Yeah, I could do it. It would be my first maintenance task ever on a port though, so I would need some guidance. Is there a good reference to read to explain what I'd need to do?
Not exactly, unfortunately. The documentation from when the project was called DarwinPorts has not been migrated to MacPorts yet, and is out of date. But you can still read it here in the Internet Archive:
http://web.archive.org/web/20060427120406/darwinports.opendarwin.org/ docs/
The best advice is to look at existing portfiles and see how they do things.
You will want to make a copy of the boost portfile:
$ cd `port dir boost` $ cp Portfile Portfile.orig
Then edit the portfile:
$ port edit boost
Then make your changes and try installing the port. Once you have a change you're happy with and want to share, get a diff of your changes:
$ diff Portfile.orig Portfile > Portfile.diff
Attach the diff to a new ticket in MacPorts' Trac installation. Then write back to the list and tell us the ticket number and someone will look at it and commit it.
You should submit unified diffs using "-u": diff -u Portfile.orig Portfile > Portfile.diff Mark
I submitted the diff at http://trac.edgewall.org/ticket/5464. Sancho On 4-Jun-07, at 3:22 PM, markd@macports.org wrote:
Ryan Schmidt <ryandesign@macports.org> on Monday, June 4, 2007 at 2:23 PM -0800 wrote:
Yeah, I could do it. It would be my first maintenance task ever on a port though, so I would need some guidance. Is there a good reference to read to explain what I'd need to do?
Not exactly, unfortunately. The documentation from when the project was called DarwinPorts has not been migrated to MacPorts yet, and is out of date. But you can still read it here in the Internet Archive:
http://web.archive.org/web/20060427120406/darwinports.opendarwin.org/ docs/
The best advice is to look at existing portfiles and see how they do things.
You will want to make a copy of the boost portfile:
$ cd `port dir boost` $ cp Portfile Portfile.orig
Then edit the portfile:
$ port edit boost
Then make your changes and try installing the port. Once you have a change you're happy with and want to share, get a diff of your changes:
$ diff Portfile.orig Portfile > Portfile.diff
Attach the diff to a new ticket in MacPorts' Trac installation. Then write back to the list and tell us the ticket number and someone will look at it and commit it.
You should submit unified diffs using "-u":
diff -u Portfile.orig Portfile > Portfile.diff
Mark
I'm afraid that you filed the patch in the Trac Trac system, instead of the MacPorts one. http://trac.macports.org Le 9 juin 07 à 19:52, Sancho McCann a écrit :
I submitted the diff at http://trac.edgewall.org/ticket/5464.
Sancho
On 4-Jun-07, at 3:22 PM, markd@macports.org wrote:
Ryan Schmidt <ryandesign@macports.org> on Monday, June 4, 2007 at 2:23 PM -0800 wrote:
Yeah, I could do it. It would be my first maintenance task ever on a port though, so I would need some guidance. Is there a good reference to read to explain what I'd need to do?
Not exactly, unfortunately. The documentation from when the project was called DarwinPorts has not been migrated to MacPorts yet, and is out of date. But you can still read it here in the Internet Archive:
http://web.archive.org/web/20060427120406/ darwinports.opendarwin.org/ docs/
The best advice is to look at existing portfiles and see how they do things.
You will want to make a copy of the boost portfile:
$ cd `port dir boost` $ cp Portfile Portfile.orig
Then edit the portfile:
$ port edit boost
Then make your changes and try installing the port. Once you have a change you're happy with and want to share, get a diff of your changes:
$ diff Portfile.orig Portfile > Portfile.diff
Attach the diff to a new ticket in MacPorts' Trac installation. Then write back to the list and tell us the ticket number and someone will look at it and commit it.
You should submit unified diffs using "-u":
diff -u Portfile.orig Portfile > Portfile.diff
Mark
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
-- Anthony Ramine, a lazy french student. nox@macports.org
Oh no! Okay, I submitted it at http://trac.macports.org/projects/ macports/ticket/12096 now. Thanks, Sancho On 9-Jun-07, at 11:27 AM, N_Ox wrote:
I'm afraid that you filed the patch in the Trac Trac system, instead of the MacPorts one. http://trac.macports.org
Le 9 juin 07 à 19:52, Sancho McCann a écrit :
I submitted the diff at http://trac.edgewall.org/ticket/5464.
Sancho
On 4-Jun-07, at 3:22 PM, markd@macports.org wrote:
Ryan Schmidt <ryandesign@macports.org> on Monday, June 4, 2007 at 2:23 PM -0800 wrote:
Yeah, I could do it. It would be my first maintenance task ever on a port though, so I would need some guidance. Is there a good reference to read to explain what I'd need to do?
Not exactly, unfortunately. The documentation from when the project was called DarwinPorts has not been migrated to MacPorts yet, and is out of date. But you can still read it here in the Internet Archive:
http://web.archive.org/web/20060427120406/ darwinports.opendarwin.org/ docs/
The best advice is to look at existing portfiles and see how they do things.
You will want to make a copy of the boost portfile:
$ cd `port dir boost` $ cp Portfile Portfile.orig
Then edit the portfile:
$ port edit boost
Then make your changes and try installing the port. Once you have a change you're happy with and want to share, get a diff of your changes:
$ diff Portfile.orig Portfile > Portfile.diff
Attach the diff to a new ticket in MacPorts' Trac installation. Then write back to the list and tell us the ticket number and someone will look at it and commit it.
You should submit unified diffs using "-u":
diff -u Portfile.orig Portfile > Portfile.diff
Mark
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
-- Anthony Ramine, a lazy french student. nox@macports.org
participants (4)
-
markd＠macports.org
-
N_Ox
-
Ryan Schmidt
-
Sancho McCann