Hi, I am rtrying to write a Portfile for Qwt, which is not build using autotools, but uses Qt's qmake + make combo. I think I have everything set, but a --preix option thst is still passed to qmake. I am trying to remove that using configure.args-delete --prefix=${prefix} but apparently that does not work. Any hints? I attach the whole Portfile for reference. Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On May 10, 2007, at 15:37, Jochen Küpper wrote:
I am rtrying to write a Portfile for Qwt, which is not build using autotools, but uses Qt's qmake + make combo.
I think I have everything set, but a --preix option thst is still passed to qmake. I am trying to remove that using configure.args-delete --prefix=${prefix} but apparently that does not work.
Any hints?
I attach the whole Portfile for reference.
MacPorts does not put the "--prefix=${prefix}" argument in the configure.args variable; it puts it in the configure.pre_args variable. Presumably you then want "configure.pre_args-delete -- prefix=${prefix}". I haven't tested this.
by default configure.pre_args contains only the --prefix parameter, so clearing the variable completely would work, too: configure.pre_args Regards, Elias On May 10, 2007, at 11:06 PM, Ryan Schmidt wrote:
On May 10, 2007, at 15:37, Jochen Küpper wrote:
I am rtrying to write a Portfile for Qwt, which is not build using autotools, but uses Qt's qmake + make combo.
I think I have everything set, but a --preix option thst is still passed to qmake. I am trying to remove that using configure.args-delete --prefix=${prefix} but apparently that does not work.
Any hints?
I attach the whole Portfile for reference.
MacPorts does not put the "--prefix=${prefix}" argument in the configure.args variable; it puts it in the configure.pre_args variable. Presumably you then want "configure.pre_args-delete -- prefix=${prefix}". I haven't tested this.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Thanks Ryan, Elias! On 10.05.2007, at 23:21, Elias Pipping wrote:
by default configure.pre_args contains only the --prefix parameter, so clearing the variable completely would work, too:
configure.pre_args
Yes, it seems to work.
On May 10, 2007, at 11:06 PM, Ryan Schmidt wrote:
MacPorts does not put the "--prefix=${prefix}" argument in the configure.args variable; it puts it in the configure.pre_args variable. Presumably you then want "configure.pre_args-delete -- prefix=${prefix}". I haven't tested this.
Where can one learn about all this stuff? If there isn't, there should really be a Wiki page with all Portfile variables. Just the names would already be helpful, although it should obviously contain an explanation in the end. Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On 11.05.2007, at 00:07, Jochen Küpper wrote:
Where can one learn about all this stuff?
Okay guys, I do have another question: How can I use local patch- files? I have put them in the local files/ directory, but port still tries to fetch them:
sudo port install ---> Fetching qwt ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- od.opendarwin.org/qwt ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- msn.opendarwin.org/qwt ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- od.opendarwin.org/ ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- msn.opendarwin.org/ Error: Target com.apple.fetch returned: fetch failed Error: Status 1 encountered during processing.
Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On May 10, 2007, at 17:07, Jochen Küpper wrote:
On 10.05.2007, at 23:21, Elias Pipping wrote:
by default configure.pre_args contains only the --prefix parameter, so clearing the variable completely would work, too:
configure.pre_args
Yes, it seems to work.
On May 10, 2007, at 11:06 PM, Ryan Schmidt wrote:
MacPorts does not put the "--prefix=${prefix}" argument in the configure.args variable; it puts it in the configure.pre_args variable. Presumably you then want "configure.pre_args-delete -- prefix=${prefix}". I haven't tested this.
Where can one learn about all this stuff?
I learned it by reading part of the source code one day. I just happened to remember the pre_args bit.
If there isn't, there should really be a Wiki page with all Portfile variables. Just the names would already be helpful, although it should obviously contain an explanation in the end.
The documentation used to have that, or at least most of the useful variables. We currently have no documentation, however.
On May 10, 2007, at 6:31 PM, Jochen Küpper wrote:
Okay guys, I do have another question: How can I use local patch- files? I have put them in the local files/ directory, but port still tries to fetch them:
It should look for them in files first, and attempt to fetch them if it can't find them for some reason. Try adding -dv to your port invocation so you can see what is going on. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On May 10, 2007, at 6:43 PM, Ryan Schmidt wrote:
If there isn't, there should really be a Wiki page with all Portfile variables. Just the names would already be helpful, although it should obviously contain an explanation in the end.
The documentation used to have that, or at least most of the useful variables. We currently have no documentation, however.
The documentation could be better, but at least they're in the porfile manpage: TARGET HOOKS A number of hooks are available for customizing many of the standard tar- gets that port(1) executes. The targets supporting these hooks are fetch, automake, autoconf, configure, build, destroot, and test. The hooks are: [snip] target.pre_args Additional arguments passed before the main arguments. Example: extract.pre_args -cd -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On May 10, 2007, at 17:31, Jochen Küpper wrote:
Okay guys, I do have another question: How can I use local patch- files? I have put them in the local files/ directory, but port still tries to fetch them:
sudo port install ---> Fetching qwt ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- od.opendarwin.org/qwt ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- msn.opendarwin.org/qwt ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- od.opendarwin.org/ ---> Attempting to fetch files/qwtconfig.pri from http://distfiles- msn.opendarwin.org/ Error: Target com.apple.fetch returned: fetch failed Error: Status 1 encountered during processing.
Did you specify the name of the patchfile as "files/qwtconfig.pri"? You don't need to specify the directory name; MacPorts knows it's going to be in the files directory. Also, your patchfile name should begin with "patch-" and end with ".diff", between which should be the name of the file that's being patched. So if your patch is patching a file called qwtconfig.pri, then you should call the file "patch- qwtconfig.pri.diff", put it in the "files" directory in your port's directory, and put "patchfiles patch-qwtconfig.pri.diff" in the portfile.
Hi Ryan, again, thanks for your help, it works ;-)
You don't need to specify the directory name; MacPorts knows it's going to be in the files directory. Also, your patchfile name should begin with "patch-" and end with ".diff", between which should be the name of the file that's being patched. So if your patch is patching a file called qwtconfig.pri, then you should call the file "patch-qwtconfig.pri.diff", put it in the "files" directory in your port's directory, and put "patchfiles patch- qwtconfig.pri.diff" in the portfile.
I have now tested and uploaded the Portfile and patch to the Trac system. Is there anything I should do in order to get the port included? What's about previous Portfiles I have added there - how often should I bug whom? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On May 10, 2007, at 3:43 PM, Ryan Schmidt wrote:
If there isn't, there should really be a Wiki page with all Portfile variables. Just the names would already be helpful, although it should obviously contain an explanation in the end.
The documentation used to have that, or at least most of the useful variables. We currently have no documentation, however.
I know all of us would love to see better documentation and a better experience on first arrival to the MacPorts site. Despite complaints from time to time, nobody has stepped up to the chore to really make things better. Some resources: - We have an xml file containing all the documentation from the old site. - We hope to bring online soon a RoR app that will, among other things, provide listings of ports. One possibility would be to also use this as a server for the site front-end and other documentation, either to be served from statically generated pages or from the database. - We also have our WordPress site in all of its unglory, which we might hack on as needed. - Or something else. - Thomas Reifferscheid at Johannes Gutenberg-Universität Mainz in germany has graciously offered some hosting and bandwidth for whatever services we need to host a site. Apple will likely also at some point have the resources to allow us to host more of our site at MacOSForge (they are currently trying to hire an admin for that site). Some vision: - We need somebody with the vision, drive, and determination to fix the documentation end of things, including pursuing one of the options above. Portmgr would love to hear from you if you'd like to pull this off. - We really need a nicely designed front-presence that describes the project and gives access to ports and documentation. Our current front end does those things only marginally. Volunteers? James
On May 10, 2007, at 4:12 PM, Jochen Küpper wrote:
Hi Ryan,
again, thanks for your help, it works ;-)
You don't need to specify the directory name; MacPorts knows it's going to be in the files directory. Also, your patchfile name should begin with "patch-" and end with ".diff", between which should be the name of the file that's being patched. So if your patch is patching a file called qwtconfig.pri, then you should call the file "patch-qwtconfig.pri.diff", put it in the "files" directory in your port's directory, and put "patchfiles patch- qwtconfig.pri.diff" in the portfile.
I have now tested and uploaded the Portfile and patch to the Trac system. Is there anything I should do in order to get the port included?
What's about previous Portfiles I have added there - how often should I bug whom?
Hey Jochen, If you've submitted a few ports and have had no uptake it's probably because others are either busy and/or uninterested in those ports. I'd encourage you to apply for a commit bit in such a case, if you're interested in maintaining ports at MacPorts. We're always looking for committers with the time and energy to make MacPorts, and its collection of ports, better. See "requesting commit rights" on this page. James.
On May 10, 2007, at 18:15, James Berry wrote:
- We really need a nicely designed front-presence that describes the project and gives access to ports and documentation. Our current front end does those things only marginally.
I've been thinking about this for awhile. I haven't fired up Photoshop yet, but I have a few ideas. I need to try to make them more concrete. I'll play with it a bit.
On May 10, 2007, at 18:12, Jochen Küpper wrote:
I have now tested and uploaded the Portfile and patch to the Trac system. Is there anything I should do in order to get the port included?
I have committed your port. Thanks for contributing. I didn't test installing it, since it requires qt4-mac and I recall that's a big package that I don't have time to build right now. I made one change: I changed INSTALLBASE=/opt/local to INSTALLBASE="$ {prefix}" (You shouldn't hard-code the /opt/local prefix because some users may install MacPorts elsewhere.)
What's about previous Portfiles I have added there - how often should I bug whom?
I don't have time at the moment. Perhaps someone else can commit them.
Hi Jochen,
What's about previous Portfiles I have added there - how often should I bug whom?
You should also manually add to the Cc: field the email address of whomever you've assigned the bug to, as documented in TracTicketing on the wiki [1] (although that may not work for macports-dev@ as the list may drop the email -- I'd check it if I weren't being lazy right now). If you missed it, though, I don't blame you, though, as I missed it when I first started submitting tickets; once the documentation effort gets going, I imagine that this will be one of the first things to be better documented. Kind regards, Maun Suang [1] http://trac.macports.org/projects/macports/wiki/TracTicketing -- Boey Maun Suang (Boey is my surname) Email: boeyms@macports.org
On 11/05/2007, at 09:15, James Berry wrote:
Volunteers?
I definitely want to help with this (as James might remember from my commit rights application :-). I should have enough free time to help lead the project in two or three months, if proves to be necessary, but unfortunately can't do so right now. As a starting point, I've created a DocumentationBrainstorming page [1]. I haven't figured out the best place to link to it from; feel free to add a link to it if you come up with a good idea for where it should go. Kind regards, Maun Suang [1] http://trac.macports.org/projects/macports/wiki/ DocumentationBrainstorming -- Boey Maun Suang (Boey is my surname) Email: boeyms@macports.org
On May 10, 2007, at 4:18 PM, James Berry wrote:
Hey Jochen,
If you've submitted a few ports and have had no uptake it's probably because others are either busy and/or uninterested in those ports. I'd encourage you to apply for a commit bit in such a case, if you're interested in maintaining ports at MacPorts. We're always looking for committers with the time and energy to make MacPorts, and its collection of ports, better. See "requesting commit rights" on this page.
And like a bone-head I didn't give the link: http:// trac.macosforge.org/projects/macports/wiki/NewCommittersGuide James
Agreed! I don't have the time nor the experience to lead any sort of organized documentation effort but I'd be happy to help out where I can. Is this something that can be done by committee? Or, better yet, wild, wild west style? It is a Wiki afterall :)
On 11.05.2007, at 01:44, Ryan Schmidt wrote:
I have committed your port. Thanks for contributing. I didn't test installing it, since it requires qt4-mac and I recall that's a big package that I don't have time to build right now.
Thanks. I have now also tested it on my Mac mini (PPC) and it works fine for me.
I made one change: I changed INSTALLBASE=/opt/local to INSTALLBASE="${prefix}" (You shouldn't hard-code the /opt/local prefix because some users may install MacPorts elsewhere.)
Thanks, I ovrlooked that (late at night;) Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
Well, I could certainly add a few lines to the "getting started" section since I just got started. But how do I edit the wiki? I created a macosforge account but I don't see any "edit this page" links in the wiki. --- James Berry <jberry@macports.org> wrote:
On May 10, 2007, at 3:43 PM, Ryan Schmidt wrote:
If there isn't, there should really be a Wiki page with all Portfile variables. Just the names would already be helpful, although it should obviously contain an explanation in the end.
The documentation used to have that, or at least most of the useful variables. We currently have no documentation, however.
I know all of us would love to see better documentation and a better experience on first arrival to the MacPorts site. Despite complaints from time to time, nobody has stepped up to the chore to really make things better.
Some resources:
- We have an xml file containing all the documentation from the old site.
- We hope to bring online soon a RoR app that will, among other things, provide listings of ports. One possibility would be to also use this as a server for the site front-end and other documentation, either to be served from statically generated pages or from the database.
- We also have our WordPress site in all of its unglory, which we might hack on as needed.
- Or something else.
- Thomas Reifferscheid at Johannes Gutenberg-Universität Mainz in germany has graciously offered some hosting and bandwidth for whatever services we need to host a site. Apple will likely also at some point have the resources to allow us to host more of our site at MacOSForge (they are currently trying to hire an admin for that site).
Some vision:
- We need somebody with the vision, drive, and determination to fix the documentation end of things, including pursuing one of the options above. Portmgr would love to hear from you if you'd like to pull this off.
- We really need a nicely designed front-presence that describes the project and gives access to ports and documentation. Our current front end does those things only marginally.
Volunteers?
James_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
____________________________________________________________________________________Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
participants (8)
-
Boey Maun Suang
-
Daniel J. Luke
-
Elias Pipping
-
James Berry
-
Jeff Adams
-
Jochen Küpper
-
Michael Thon
-
Ryan Schmidt