From mark.duling at biola.edu Mon Jan 1 08:51:47 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:53 2007 Subject: [MacPorts] #10778: UPDATE: pmk-0.9.2 to latest In-Reply-To: <057.5e817c21dafc016e212545ede42c5e9f@macosforge.org> References: <048.31f0b5c8d8f22df3c13a809da18618d7@macosforge.org> <057.5e817c21dafc016e212545ede42c5e9f@macosforge.org> Message-ID: Has it been tested on Intel? I corresponded with the developer and last I knew he has yet to figure out how to make it work on Intel Macs. Here's the sourceforge bug report. http://sourceforge.net/tracker/index.php?func=detail&aid=1569713&group_id=94395&atid=607694 I'm on vacation and have limited internet access or I'd try it myself. Mark >#10778: UPDATE: pmk-0.9.2 to latest >--------------------------------+------------------------------------------- > Reporter: wyuenho@gmail.com | Owner: yeled@macports.org > Type: enhancement | Status: new > Priority: Nice to have | Component: ports > Version: 1.3.2 | Severity: Other >Resolution: | Keywords: >--------------------------------+------------------------------------------- >Comment (by wyuenho@gmail.com): > > pmk has already been upgraded to 0.10.1. This bug can be closed now. > >-- >Ticket URL: >MacPorts >Ports system for Mac OS From wyuenho at gmail.com Mon Jan 1 09:08:00 2007 From: wyuenho at gmail.com (Yuen Ho Wong) Date: Tue Oct 9 16:39:54 2007 Subject: [MacPorts] #10778: UPDATE: pmk-0.9.2 to latest In-Reply-To: References: <048.31f0b5c8d8f22df3c13a809da18618d7@macosforge.org> <057.5e817c21dafc016e212545ede42c5e9f@macosforge.org> Message-ID: <45993FF0.1000203@gmail.com> No. I have only tested this port on a iBook G4. I don't have an Intel Mac to test this port. Maybe someone who has one can help? Yuen Ho Wong Mark Duling wrote: > Has it been tested on Intel? I corresponded with the developer and last I > knew he has yet to figure out how to make it work on Intel Macs. Here's > the sourceforge bug report. > > http://sourceforge.net/tracker/index.php?func=detail&aid=1569713&group_id=94395&atid=607694 > > I'm on vacation and have limited internet access or I'd try it myself. > > Mark > > >> #10778: UPDATE: pmk-0.9.2 to latest >> --------------------------------+------------------------------------------- >> Reporter: wyuenho@gmail.com | Owner: yeled@macports.org >> Type: enhancement | Status: new >> Priority: Nice to have | Component: ports >> Version: 1.3.2 | Severity: Other >> Resolution: | Keywords: >> --------------------------------+------------------------------------------- >> Comment (by wyuenho@gmail.com): >> >> pmk has already been upgraded to 0.10.1. This bug can be closed now. >> >> -- >> Ticket URL: >> MacPorts >> Ports system for Mac OS >> > > > From sbranzo at gmail.com Tue Jan 2 04:26:16 2007 From: sbranzo at gmail.com (Sbranzo) Date: Tue Oct 9 16:39:54 2007 Subject: New slrn-dev port Message-ID: <20070102122616.GA29671@sbranzo.local> Hi, I'm trying to write a new slrn-dev port using the same cvs snapshot used in debian-unstable. To do this I think I need to execute some commands between the various phases of the automated process: 1) The name of the sources tarball is slrn_0.9.8.1pl2~cvs20061116.orig.tar.gz, but the enclosed folder is called slrn-0.9.8.1pl2cvs20061116 ("-" instead of "_" and w/o .orig) How could I workaround this? Now I simply use slrn-0.9.8.1pl2cvs20061116 as distname, but I have to manually place sources in /opt/local[..]/distfiles/slrn-0.9.8.1pl2[..].tar.gz 2) Inside the autoconf directory a couple of links are wrong. They point to /usr/share/automake-1.9/ and on tiger I have automake-1.6. Is this a common problem? (which is a different way of asking for a common solution ;-) I'm using the current slrn portfile as a base, and I'm not sure it's completely correct in the ssl variant, because it explicitly points to /usr/lib. If it's needed I can send the portfile I'm writing. TIA, Gufo From frank.mcpherson at janusresearch.com Wed Jan 3 04:37:22 2007 From: frank.mcpherson at janusresearch.com (Frank Mcpherson) Date: Tue Oct 9 16:39:54 2007 Subject: Request Update/Commit: mysql4 to version 4.1.22 Message-ID: <7F53AC86-F053-438A-9EAF-BE2AB4955FCA@janusresearch.com> I hope I'm not stepping on anyone's toes here, but I use this port on a production server so I'm interested in seeing it track security updates. I emailed both the listed maintainers a couple days ago but got no response. Could someone with commit authority please commit this change? 4.1.21 contains an important security patch, and 4.1.22 contains a bunch of bugfixes. I've entered a Trac ticket with the patch to update this port to 4.1.22; all it needs is a version number bump and matching md5 sum change. http://trac.macports.org/projects/macports/ticket/11210 Thanks in advance, Frank From giulio.eulisse at cern.ch Wed Jan 3 05:38:09 2007 From: giulio.eulisse at cern.ch (Giulio Eulisse) Date: Tue Oct 9 16:39:54 2007 Subject: Fetching multiple modules from CVS. Message-ID: Ciao, I'm writing a few ports for some of the projects I'm working on. One of them requires the fetching of multiple modules from different CVS servers. Is there a way of doing so in an automatic way, or should I completely override the "fetch" phase and do it all by myself? In general, how does macports handle multiple sources? Ciao, Giulio From eridius at macports.org Wed Jan 3 13:29:01 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: Request Update/Commit: mysql4 to version 4.1.22 In-Reply-To: <7F53AC86-F053-438A-9EAF-BE2AB4955FCA@janusresearch.com> References: <7F53AC86-F053-438A-9EAF-BE2AB4955FCA@janusresearch.com> Message-ID: Alright, Committed in r21120. Should show up in the rsync mirror within 12 hours. On Jan 3, 2007, at 7:37 AM, Frank Mcpherson wrote: > I hope I'm not stepping on anyone's toes here, but I use this port > on a production server so I'm interested in seeing it track > security updates. I emailed both the listed maintainers a couple > days ago but got no response. Could someone with commit authority > please commit this change? > > 4.1.21 contains an important security patch, and 4.1.22 contains a > bunch of bugfixes. I've entered a Trac ticket with the patch to > update this port to 4.1.22; all it needs is a version number bump > and matching md5 sum change. > > http://trac.macports.org/projects/macports/ticket/11210 -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070103/d324ecc0/attachment.html From eridius at macports.org Wed Jan 3 15:08:51 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: Bug in port name handling In-Reply-To: References: <20070103192014.GA16756@sbranzo.local> Message-ID: It appears, from looking at the source, that the registry only matches the following characters in the version: - _ a-z A-Z 0-9 . Perhaps this should be modified. I would suggest matching everything besides, say, a space here. Everything else should be fine, because the routine here (receipt_flat::installed) will always be passed a version of the form version_revision[+variants], which means it will always end with _digit (followed by optional variants). So whatever the version regex matches, it won't accidentally suck up revision and variants, because it can't (caveat: if a variant is named foobar_0 it could, though I would say a variant should never be named like that, but if you want to eliminate this problem then disallow plusses in the version string too). So basically, if you want the ~ character, MacPorts needs modification. In the meantime I'd suggest using a dash. I've CC'ed the dev list - anybody have any thoughts on modifying the version-matching regex here? And does anybody know of any other locations where the version is matched against a regex? Final thoughts: I just remembered that this same routine uses glob to find the version directory, so versions would also have to restrict asterisks, questionmarks, braces, brackets, and backslashes (basically, anything that's special to glob). But my stance is the more liberal we can make the version matching, the better. On Jan 3, 2007, at 5:41 PM, Kevin Ballard wrote: > I'm guessing it doesn't like the ~ character. > > [snip] > > On Jan 3, 2007, at 2:20 PM, Sbranzo wrote: >> I thinks there's a bug in the way port names are handled. >> I'm trying to compile a cvs snapshot of slrn, the same present in >> debian >> experimental. The debian maintainer assigned >> 0.9.8.1pl2~cvs20061116 as >> version number, and I wish to keep this convention. -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070103/626e0c98/attachment.html From dluke at geeklair.net Wed Jan 3 16:58:42 2007 From: dluke at geeklair.net (Daniel J. Luke) Date: Tue Oct 9 16:39:54 2007 Subject: Bug in port name handling In-Reply-To: References: <20070103192014.GA16756@sbranzo.local> Message-ID: <43D21C20-335C-4413-BD05-DB1C645B0B33@geeklair.net> On Jan 3, 2007, at 6:08 PM, Kevin Ballard wrote: > I've CC'ed the dev list - anybody have any thoughts on modifying > the version-matching regex here? And does anybody know of any other > locations where the version is matched against a regex? > > Final thoughts: I just remembered that this same routine uses glob > to find the version directory, so versions would also have to > restrict asterisks, questionmarks, braces, brackets, and > backslashes (basically, anything that's special to glob). But my > stance is the more liberal we can make the version matching, the > better. We had a bunch of problems in the past with more liberal name allowances and ended up being this restrictive to prevent future problems. I'm not sure if the people who worked on this before are still around to comment or not. In any case, any changes to this would need a lot of testing to be sure it doesn't break more than it fixes. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20070103/ecc122cf/PGP.bin From mccdo at iastate.edu Wed Jan 3 18:48:54 2007 From: mccdo at iastate.edu (Doug McCorkle) Date: Tue Oct 9 16:39:54 2007 Subject: gmtl port file Message-ID: Hello, I have a port file for gmtl that I would like considered for addition to macports. Please let me know if the file needs to be updated in some manner to be included. Thanks for the consideration. Doug -------------- next part -------------- A non-text attachment was scrubbed... Name: Portfile Type: application/octet-stream Size: 642 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20070103/150e149c/Portfile.obj -------------- next part -------------- From erickt at macports.org Thu Jan 4 10:06:20 2007 From: erickt at macports.org (Erick Tryzelaar) Date: Tue Oct 9 16:39:54 2007 Subject: can someone check these port patches for me? Message-ID: <459D421C.2030008@macports.org> I seem to have lost access / forgot my password to the subversion server, and I can't check these updates in. Could someone do it for me? -e Index: py-scipy/Portfile =================================================================== --- py-scipy/Portfile (revision 21120) +++ py-scipy/Portfile (working copy) @@ -4,7 +4,7 @@ PortGroup python24 1.0 name py-scipy -version 0.5.1 +version 0.5.2 revision 0 categories python platforms darwin @@ -16,9 +16,9 @@ master_sites sourceforge:scipy distname scipy-${version} -checksums md5 48442a427f0556ad2ad1721dd62e401c \ - sha1 bed9be244fc73c96a252184cfc14653035832f7e \ - rmd160 60a184b57f50e9bef78843cbe96542aee43ac386 +checksums md5 e24387ac7f9e589816364db7c64c3185 \ + sha1 879cfdbb2b2f7a8616737f828cd01790d222a636 \ + rmd160 fa945185df7fc48e03bafdddeaaea72a8eb4914d depends_lib lib:gnuplot:gnuplot \ port:py-numpy Index: py-numpy/Portfile =================================================================== --- py-numpy/Portfile (revision 21120) +++ py-numpy/Portfile (working copy) @@ -4,7 +4,7 @@ PortGroup python24 1.0 name py-numpy -version 1.0b5 +version 1.0.1 revision 0 categories python platforms darwin @@ -16,9 +16,9 @@ master_sites sourceforge:numpy distname numpy-${version} -checksums md5 2451bc1751a9bc1c22452cd71f846982 \ - sha1 001797105ba9924f50dc1115b5d5eaf1673e4d30 \ - rmd160 994baabc9df870dcdf5fbf62b1789e0d5fcb417b +checksums md5 13a29244cbe03e0d45e56d8d90ecb55d \ + sha1 d6d20a32d2386ea32582d497d123211a98441c4e \ + rmd160 f3a0c55aa5add8c93f91eee1bb05ff555c0f2485 depends_lib-append lib:fftw:fftw-3 From ryandesign at macports.org Thu Jan 4 11:35:48 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:39:54 2007 Subject: can someone check these port patches for me? In-Reply-To: <459D421C.2030008@macports.org> References: <459D421C.2030008@macports.org> Message-ID: On Jan 4, 2007, at 12:06, Erick Tryzelaar wrote: > I seem to have lost access / forgot my password to the subversion > server, and I can't check these updates in. Could someone do it for > me? Done. > Index: py-scipy/Portfile > =================================================================== > --- py-scipy/Portfile (revision 21120) > +++ py-scipy/Portfile (working copy) > @@ -4,7 +4,7 @@ > PortGroup python24 1.0 > name py-scipy > -version 0.5.1 > +version 0.5.2 > revision 0 > categories python > platforms darwin > @@ -16,9 +16,9 @@ > master_sites sourceforge:scipy > distname scipy-${version} > -checksums md5 48442a427f0556ad2ad1721dd62e401c \ > - sha1 > bed9be244fc73c96a252184cfc14653035832f7e \ > - rmd160 > 60a184b57f50e9bef78843cbe96542aee43ac386 > +checksums md5 e24387ac7f9e589816364db7c64c3185 \ > + sha1 > 879cfdbb2b2f7a8616737f828cd01790d222a636 \ > + rmd160 > fa945185df7fc48e03bafdddeaaea72a8eb4914d > depends_lib lib:gnuplot:gnuplot \ > port:py-numpy Done in revision 21123. > Index: py-numpy/Portfile > =================================================================== > --- py-numpy/Portfile (revision 21120) > +++ py-numpy/Portfile (working copy) > @@ -4,7 +4,7 @@ > PortGroup python24 1.0 > name py-numpy > -version 1.0b5 > +version 1.0.1 > revision 0 > categories python > platforms darwin > @@ -16,9 +16,9 @@ > master_sites sourceforge:numpy > distname numpy-${version} > -checksums md5 2451bc1751a9bc1c22452cd71f846982 \ > - sha1 > 001797105ba9924f50dc1115b5d5eaf1673e4d30 \ > - > rmd160 > 994baabc9df870dcdf5fbf62b1789e0d5fcb417b > +checksums md5 13a29244cbe03e0d45e56d8d90ecb55d \ > + sha1 > d6d20a32d2386ea32582d497d123211a98441c4e \ > + rmd160 > f3a0c55aa5add8c93f91eee1bb05ff555c0f2485 > depends_lib-append lib:fftw:fftw-3 Done in revision 21124. From erickt at macports.org Thu Jan 4 13:26:08 2007 From: erickt at macports.org (Erick Tryzelaar) Date: Tue Oct 9 16:39:54 2007 Subject: can someone check these port patches for me? In-Reply-To: References: <459D421C.2030008@macports.org> Message-ID: <459D70F0.2030301@macports.org> Thanks Ryan! Ryan Schmidt wrote: > On Jan 4, 2007, at 12:06, Erick Tryzelaar wrote: > >> I seem to have lost access / forgot my password to the subversion >> server, and I can't check these updates in. Could someone do it for me? > > Done. > > >> Index: py-scipy/Portfile >> =================================================================== >> --- py-scipy/Portfile (revision 21120) >> +++ py-scipy/Portfile (working copy) >> @@ -4,7 +4,7 @@ >> PortGroup python24 1.0 >> name py-scipy >> -version 0.5.1 >> +version 0.5.2 >> revision 0 >> categories python >> platforms darwin >> @@ -16,9 +16,9 @@ >> master_sites sourceforge:scipy >> distname scipy-${version} >> -checksums md5 48442a427f0556ad2ad1721dd62e401c \ >> - sha1 bed9be244fc73c96a252184cfc14653035832f7e \ >> - rmd160 60a184b57f50e9bef78843cbe96542aee43ac386 >> +checksums md5 e24387ac7f9e589816364db7c64c3185 \ >> + sha1 879cfdbb2b2f7a8616737f828cd01790d222a636 \ >> + rmd160 fa945185df7fc48e03bafdddeaaea72a8eb4914d >> depends_lib lib:gnuplot:gnuplot \ >> port:py-numpy > > Done in revision 21123. > > >> Index: py-numpy/Portfile >> =================================================================== >> --- py-numpy/Portfile (revision 21120) >> +++ py-numpy/Portfile (working copy) >> @@ -4,7 +4,7 @@ >> PortGroup python24 1.0 >> name py-numpy >> -version 1.0b5 >> +version 1.0.1 >> revision 0 >> categories python >> platforms darwin >> @@ -16,9 +16,9 @@ >> master_sites sourceforge:numpy >> distname numpy-${version} >> -checksums md5 2451bc1751a9bc1c22452cd71f846982 \ >> - sha1 001797105ba9924f50dc1115b5d5eaf1673e4d30 \ >> - >> rmd160 >> 994baabc9df870dcdf5fbf62b1789e0d5fcb417b >> +checksums md5 13a29244cbe03e0d45e56d8d90ecb55d \ >> + sha1 d6d20a32d2386ea32582d497d123211a98441c4e \ >> + rmd160 f3a0c55aa5add8c93f91eee1bb05ff555c0f2485 >> depends_lib-append lib:fftw:fftw-3 > > Done in revision 21124. > > From eridius at macports.org Fri Jan 5 21:17:55 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: Fwd: SourceForge in mirror_sites.tcl References: Message-ID: <89D40965-8304-4C23-AE66-3CF7B884E3A2@macports.org> This was sent to the Users list. It's probably more appropriate for this list. Begin forwarded message: > From: Ross David Turk > Date: January 5, 2007 3:58:05 PM EST > To: macports-users@lists.macosforge.org > Subject: SourceForge in mirror_sites.tcl > > Hey folks! > > I noticed that you guys are fetching SourceForge files from the > mirrors directly, and did a little grepping. I'm not a macports/ > darwinports expert (or even a heavy user), but I think that it's > set in mirror_sites.tcl: > > set portfetch::mirror_sites::sites(sourceforge) { > http://easynews.dl.sourceforge.net/ > http://surfnet.dl.sourceforge.net/ > http://belnet.dl.sourceforge.net/ > http://heanet.dl.sourceforge.net/ > http://ovh.dl.sourceforge.net/ > http://internap.dl.sourceforge.net/ > http://jaist.dl.sourceforge.net/ > http://umn.dl.sourceforge.net/ > http://kent.dl.sourceforge.net/ > http://mesh.dl.sourceforge.net/ > http://ufpr.dl.sourceforge.net/ > http://nchc.dl.sourceforge.net/ > http://switch.dl.sourceforge.net/ > http://superb-west.dl.sourceforge.net/ > } > > In the old days, until about a month ago, users accessing a file > like http://prdownloads.sourceforge.net/gaim/gaim-1.5.0.exe would > be sent to a mirror selection page. Recently, we replaced that > page with a more intelligent download redirector. > > I would love to see you change the snippet above to: > > set portfetch::mirror_sites::sites(sourceforge) { > http://downloads.sourceforge.net/ > } > > Doing this should provide these benefits: > > 1) You won't have to manage the mirror list as mirrors are added or > removed. > 2) You can ensure that the mirror you're sent to has the file > you're looking for. Not all mirrors have all files. > 3) Your users will probably get a faster download due to the > geolocation. > 4) SourceForge projects will get fair download statistics - going > to the mirror directly bypasses our statistics hooks, so your > downloads haven't been counting towards their SourceForge.net > project activity rating. > > The risk is, of course, that if the SF.net website goes down, so > will your ability to get these files. Perhaps you could list > http://downloads.sourceforge.net first and keep a few other ones in > there as a backup in case we're down? Does port try to fetch from > the mirrors using the listed order? > > Let me know if you have any questions.. :) > > Thanks! > Ross > > -- > Ross David Turk > SourceForge.net Community Manager -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070106/b0a03d65/attachment.html From mccdo at iastate.edu Sat Jan 6 13:32:02 2007 From: mccdo at iastate.edu (Doug McCorkle) Date: Tue Oct 9 16:39:54 2007 Subject: gmtl port file In-Reply-To: References: Message-ID: <5BC13B46-E7F3-42CD-B8E1-8B9CBFE698D6@iastate.edu> On Jan 3, 2007, at 8:48 PM, Doug McCorkle wrote: > Hello, > I have a port file for gmtl that I would like considered for > addition to macports. Please let me know if the file needs to be > updated in some manner to be included. Thanks for the consideration. > Were there any thoughts on this Portfile? Do I need to submit it to another venue for review or consideration? Thanks. Doug From mark.duling at biola.edu Mon Jan 8 14:48:12 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:54 2007 Subject: gmtl port file In-Reply-To: References: Message-ID: Doug McCorkle on Wednesday, January 3, 2007 at 6:48 PM -0800 wrote: > I have a port file for gmtl that I would like considered for >addition to macports. Please let me know if the file needs to be >updated in some manner to be included. Thanks for the consideration. Doug, I tried it and I have only two questions based on this: ------------------------------------- Building GMTL Version: 0.4.12 Install prefix: /opt/local/var/db/dports/build/_Users_mduling_dports_math_gmtl/work/destroot/opt/local checking for CppUnitDir [/usr/local/include]... no checking for EnablePython [False]... Using Boost version 1.31 checking for BoostPythonDir [/usr/local]... /usr/local/include/boost/version.hpp not found. Trying /usr/local/include/boost-1_31/boost/version.hpp /usr/local/include/boost-1_31/boost/version.hpp not found. ------------------------------------- 1) Should the app be compiled with boost support? If so a dependency for it should be added for the MP version and a switch or configure patch to point gmtl to the MP one. 2) Or should boost support be turned off, or only off by default with optional support provided with a boost variant? 3) If boost support is added one way or another, then unless there are special circumstances (and there could be because I am not in a position to know) then the port should not look for a non-MP boost (in /usr). As it is now the port will 4) The same questions hold for CppUnitDir, whatever that is. After getting these issues resolved you should submit the portfile as an attachment to a Trac ticket, though sometimes you need to prod someone to commit it with a list message to get it soon. Mark From roederja at student.ethz.ch Mon Jan 8 16:53:36 2007 From: roederja at student.ethz.ch (=?UTF-8?B?SmFubiBSw7ZkZXI=?=) Date: Tue Oct 9 16:39:54 2007 Subject: System libraries vs. Macports installed libraries Message-ID: Hi all, I was wondering whether there is a policy for which library to use if a version of that library comes with MacOS X and there's also a port available. Specifically I'm talking about the openssl port/library. If both approaches work, which library should a port link against ? Jann From ryandesign at macports.org Mon Jan 8 17:21:55 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:39:54 2007 Subject: System libraries vs. Macports installed libraries In-Reply-To: References: Message-ID: <82F9DFF3-DFC6-4F1F-A8D9-C7ED348F2B7E@macports.org> On Jan 8, 2007, at 18:53, Jann R?der wrote: > I was wondering whether there is a policy for which library to use > if a > version of that library comes with MacOS X and there's also a port > available. Specifically I'm talking about the openssl port/library. If > both approaches work, which library should a port link against ? Use the MacPorts version unless there's a really good reason not to. http://trac.macosforge.org/projects/macports/wiki/ FAQ#WhyisMacPortsusingitsownlibraries From peter at pogma.com Tue Jan 9 04:59:39 2007 From: peter at pogma.com (Peter O'Gorman) Date: Tue Oct 9 16:39:54 2007 Subject: System libraries vs. Macports installed libraries In-Reply-To: <82F9DFF3-DFC6-4F1F-A8D9-C7ED348F2B7E@macports.org> References: <82F9DFF3-DFC6-4F1F-A8D9-C7ED348F2B7E@macports.org> Message-ID: <52922DDB-D290-4463-A169-F22B906F6AE0@pogma.com> On Jan 9, 2007, at 10:21 AM, Ryan Schmidt wrote: > On Jan 8, 2007, at 18:53, Jann R?der wrote: > >> I was wondering whether there is a policy for which library to use >> if a >> version of that library comes with MacOS X and there's also a port >> available. Specifically I'm talking about the openssl port/ >> library. If >> both approaches work, which library should a port link against ? > > Use the MacPorts version unless there's a really good reason not to. > > http://trac.macosforge.org/projects/macports/wiki/ > FAQ#WhyisMacPortsusingitsownlibraries OpenSSL is a bit of an exception, I think. http://www.gnome.org/~markmc/openssl-and-the-gpl.html http://www.openssl.org/support/faq.html http://en.wikipedia.org/wiki/OpenSSL etc etc etc. The system openssl should probably be used for GPLed programs without an exception. Anyway, now that I've brought that up, I'd better disappear :-) Peter From mccdo at iastate.edu Tue Jan 9 11:37:56 2007 From: mccdo at iastate.edu (Doug McCorkle) Date: Tue Oct 9 16:39:54 2007 Subject: gmtl port file In-Reply-To: References: Message-ID: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> On Jan 8, 2007, at 4:48 PM, Mark Duling wrote: > Doug McCorkle on Wednesday, January 3, 2007 at > 6:48 PM > -0800 wrote: >> I have a port file for gmtl that I would like considered for >> addition to macports. Please let me know if the file needs to be >> updated in some manner to be included. Thanks for the consideration. > > Doug, > > I tried it and I have only two questions based on this: > > ------------------------------------- > Building GMTL Version: 0.4.12 > Install prefix: > /opt/local/var/db/dports/build/_Users_mduling_dports_math_gmtl/work/ > destroot/opt/local > checking for CppUnitDir [/usr/local/include]... > no > checking for EnablePython [False]... > Using Boost version 1.31 > checking for BoostPythonDir [/usr/local]... > /usr/local/include/boost/version.hpp not found. > Trying /usr/local/include/boost-1_31/boost/version.hpp > /usr/local/include/boost-1_31/boost/version.hpp not found. > ------------------------------------- > > 1) Should the app be compiled with boost support? If so a > dependency for > it should be added for the MP version and a switch or configure > patch to > point gmtl to the MP one. > 2) Or should boost support be turned off, or only off by default with > optional support provided with a boost variant? > 3) If boost support is added one way or another, then unless there are > special circumstances (and there could be because I am not in a > position > to know) then the port should not look for a non-MP boost (in / > usr). As > it is now the port will > 4) The same questions hold for CppUnitDir, whatever that is. > For basic development usage boost and cppunit are not needed. I figured after it was in use for a little while the other variants could be added. I talked with the developers of the library and they did not seem to think it was an immediate requirement to have the other variants available. I will see if it is possible to disable the boost and cppunit requirement. > After getting these issues resolved you should submit the portfile > as an > attachment to a Trac ticket, though sometimes you need to prod > someone to > commit it with a list message to get it soon. > > Mark > Thanks for trying it out and the feedback! Doug From cedric.luthi at gmail.com Fri Jan 12 02:47:29 2007 From: cedric.luthi at gmail.com (=?ISO-8859-1?Q?C=E9dric_Luthi?=) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket #11233 commit Message-ID: <516D45B6-88C7-4D54-86F0-5040FA57F54A@gmail.com> Hello, It would be nice if someone commits this patch http://trac.macports.org/projects/macports/ticket/11233 Regards. C?dric Luthi From deric at caveo.se Fri Jan 12 07:17:56 2007 From: deric at caveo.se (Daniel Ericsson) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket #11233 commit In-Reply-To: <516D45B6-88C7-4D54-86F0-5040FA57F54A@gmail.com> References: <516D45B6-88C7-4D54-86F0-5040FA57F54A@gmail.com> Message-ID: <41091AEE-B81A-4E57-A82A-4DAF4CDFEDD6@caveo.se> On 12 jan 2007, at 11.47, C?dric Luthi wrote: > Hello, > It would be nice if someone commits this patch > http://trac.macports.org/projects/macports/ticket/11233 Tested and commited. - Daniel From eridius at macports.org Fri Jan 12 11:27:36 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: darwinports_fastload source iteration Message-ID: <54EC052E-6785-4D20-A9CC-297AB71F7846@macports.org> I was just poking around and in darwinports_fastload.tcl.in I discovered the following: # I could iterate on the directory, but the only way I know in Tcl involves a # native function we provide in pextlib. set dir [file join "@prefix_expanded@" share darwinports Tcl port1.0] catch {source [file join $dir pkgIndex.tcl]} set dir [file join "@prefix_expanded@" share darwinports Tcl package1.0] catch {source [file join $dir pkgIndex.tcl]} set dir [file join "@prefix_expanded@" share darwinports Tcl pextlib1.0] catch {source [file join $dir pkgIndex.tcl]} set dir [file join "@prefix_expanded@" share darwinports Tcl registry1.0] catch {source [file join $dir pkgIndex.tcl]} It's actually rather trivial to do this iteration - that block can be replaced with: foreach dir [glob -directory "@prefix_expanded@" -join share darwinports Tcl *] { catch {source [file join $dir pkgIndex.tcl]} } Should I go ahead and commit this change? Incidentally, this will source darwintrace1.0/pkgIndex.tcl (which the manual sourcing doesn't), but I looked in that file and it's just comments, so it won't make a difference. I am curious as to what darwintrace1.0 is for, since it doesn't provide any packages in pkgIndex.tcl. -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070112/59a6311e/attachment.html From mccdo at iastate.edu Sat Jan 13 19:10:46 2007 From: mccdo at iastate.edu (Doug McCorkle) Date: Tue Oct 9 16:39:54 2007 Subject: gmtl port file In-Reply-To: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> References: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> Message-ID: I have uploaded a new portfile that looks at the new sourceforge server. Could this ticket be reviewed: http://trac.macosforge.org/projects/macports/ticket/11232 I did not find a way to disable looking for cppunit or boost. Doug On Jan 9, 2007, at 1:37 PM, Doug McCorkle wrote: > > On Jan 8, 2007, at 4:48 PM, Mark Duling wrote: > >> Doug McCorkle on Wednesday, January 3, 2007 at >> 6:48 PM >> -0800 wrote: >>> I have a port file for gmtl that I would like considered for >>> addition to macports. Please let me know if the file needs to be >>> updated in some manner to be included. Thanks for the consideration. >> >> Doug, >> >> I tried it and I have only two questions based on this: >> >> ------------------------------------- >> Building GMTL Version: 0.4.12 >> Install prefix: >> /opt/local/var/db/dports/build/_Users_mduling_dports_math_gmtl/ >> work/destroot/opt/local >> checking for CppUnitDir [/usr/local/include]... >> no >> checking for EnablePython [False]... >> Using Boost version 1.31 >> checking for BoostPythonDir [/usr/local]... >> /usr/local/include/boost/version.hpp not found. >> Trying /usr/local/include/boost-1_31/boost/version.hpp >> /usr/local/include/boost-1_31/boost/version.hpp not found. >> ------------------------------------- >> >> 1) Should the app be compiled with boost support? If so a >> dependency for >> it should be added for the MP version and a switch or configure >> patch to >> point gmtl to the MP one. >> 2) Or should boost support be turned off, or only off by default with >> optional support provided with a boost variant? >> 3) If boost support is added one way or another, then unless there >> are >> special circumstances (and there could be because I am not in a >> position >> to know) then the port should not look for a non-MP boost (in / >> usr). As >> it is now the port will >> 4) The same questions hold for CppUnitDir, whatever that is. >> > For basic development usage boost and cppunit are not needed. I > figured after it was in use for a little while the other variants > could be added. I talked with the developers of the library and > they did not seem to think it was an immediate requirement to have > the other variants available. I will see if it is possible to > disable the boost and cppunit requirement. > >> After getting these issues resolved you should submit the portfile >> as an >> attachment to a Trac ticket, though sometimes you need to prod >> someone to >> commit it with a list message to get it soon. >> >> Mark >> > > Thanks for trying it out and the feedback! > > Doug From mark.duling at biola.edu Sun Jan 14 00:06:25 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:54 2007 Subject: Developer requesting deletion of port Message-ID: A developer is requesting we delete a port of his. I know MarKus has not been active for awhile. http://trac.macosforge.org/projects/macports/ticket/11072 The request seems reasonable. Any objections to deleting the port? Mark From sal at ri.cmu.edu Sun Jan 14 08:05:29 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:54 2007 Subject: darwinports.com [was: Developer requesting deletion of port] In-Reply-To: References: Message-ID: o A developer is requesting we delete a port of his. I know MarKus has o not been active for awhile. Seems reasonable to me. Is there really nothing we can do about the *.darwinports.com sites? We, as a community, have decided it is a problem. The owner, from the e-mails, claims to want to support (or even be a member of) that community, but acts in contradiction to that claim. The site routinely causes confusion. I've looked through our archives, and the issue seems to have dead-ended at opendarwin trying to buy the site from its owner. The site clearly makes money for its owner and makes it more difficult for people to find our site. Question: 1) We do not have a standard BSD or GPL license. How hard would it be for us to add a term to base/LICENSE that requires any sites attempting to reproduce or mirror information from our site or repository to place a banner a the top of each page indicating that it is duplicating information from our site. 2) In spite of our open source license, I believe that those sites are actually tortuous interference (if not fraud) and open us to legal remedy. If we have any lawyers on this list (which seems unlikely) or on -users (which seems more likely), we could ask for a letter to be drawn up. The ad revenue alone makes this a legal issue. 3) The site contains links to "Powered By DarwinPorts" that point to that site, not ours, which is, at best, misdirection. 4) Since Darwinports.com is using Google AdSense, Google may be particularly sensitive to its fraudulent nature of the site, since having an misleadingly increased page rank that drives revenue to Google could be percieved as Google biasing its listings to improve its own revenue (a claim which it vehemently denies). We could write a letter to Google and ask for their advice on the matter as a starting point. It annoys me, of course, that we work for free and that this site makes money off of it while causing us more work. Since I'm not coding much on MP these days (though I should really get my bit set so I can commit all these ports I keep writing for myself), I wouldn't mind doing some legwork for this. I think I'm in a bad mood this morning. -- Sal P.S. I assume that the site owner is on this list, so please bear in mind that all exchanges on this topic to date have been courteous. smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sun, 14 Jan 2007, Mark Duling wrote: o o http://trac.macosforge.org/projects/macports/ticket/11072 o o The request seems reasonable. Any objections to deleting the port? o o Mark o o _______________________________________________ o macports-dev mailing list o macports-dev@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-dev o o From pmq at macports.org Sun Jan 14 08:23:17 2007 From: pmq at macports.org (Pierre Queinnec) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts Message-ID: <45AA58F5.6010502@macports.org> Hi all, Eridius pointed me on IRC to MacFUSE, the recently released FUSE port to OS X. I wanted to see if there is interest in having it in our ports. There is a major drawback in having kernel modules in the ports in the fact that it's a tad easier for curious & inexperienced users to mess up their systems. Of course, it's also a lot cooler for some of us to just install sshfs and make it work without spending too much time. This drawback could probably be addressed by having a separate category (something called 'kernel' for example) where we'd warn users that they can mess their systems up if they don't know what they're doing. My first question is wether we want kexts in MacPorts at once. FUSE would be a fine addition then, we could also add something like a tun/tap device. If we are to just distribute the userland stuff, it's going to be harder to get users to update their kexts to match the userland libs versions. Thoughts on this? -- Pierre From sal at ri.cmu.edu Sun Jan 14 08:55:37 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts In-Reply-To: <45AA58F5.6010502@macports.org> References: <45AA58F5.6010502@macports.org> Message-ID: I think this is a valid and useful extension of MP's mission. -- Sal smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sun, 14 Jan 2007, Pierre Queinnec wrote: o Hi all, o o Eridius pointed me on IRC to MacFUSE, the recently released FUSE port to OS X. o I wanted to see if there is interest in having it in our ports. o o There is a major drawback in having kernel modules in the ports in the fact o that it's a tad easier for curious & inexperienced users to mess up their o systems. Of course, it's also a lot cooler for some of us to just install o sshfs and make it work without spending too much time. This drawback could o probably be addressed by having a separate category (something called 'kernel' o for example) where we'd warn users that they can mess their systems up if they o don't know what they're doing. o o My first question is wether we want kexts in MacPorts at once. FUSE would be a o fine addition then, we could also add something like a tun/tap device. If we o are to just distribute the userland stuff, it's going to be harder to get o users to update their kexts to match the userland libs versions. o o Thoughts on this? o -- Pierre o _______________________________________________ o macports-dev mailing list o macports-dev@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-dev o o From kw at codebykevin.com Sun Jan 14 09:05:35 2007 From: kw at codebykevin.com (Kevin Walzer) Date: Tue Oct 9 16:39:54 2007 Subject: darwinports.com [was: Developer requesting deletion of port] In-Reply-To: References: Message-ID: <45AA62DF.3060802@codebykevin.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Salvatore Domenick Desiano wrote: > > 1) We do not have a standard BSD or GPL license. How hard would it be > for us to add a term to base/LICENSE that requires any sites > attempting to reproduce or mirror information from our site or > repository to place a banner a the top of each page indicating that it > is duplicating information from our site. > In terms of intellectual property, this is more an issue of trademark than of copyright--the brand identity of MacPorts/DarwinPorts instead of complying with the licensing terms of the source code. These are not contradictory--the Mozilla Foundation places extensive restrictions on how the Firefox and Mozilla trademarks can be used, even with an open-source license. Of course, to assert a trademark, there needs to be some legal entity set up to do so. Trademark registration is not required to assert the trademark use, although it makes things easier. For an example of how to do this, see this link: http://fink.sourceforge.net/legal.php - -- Kevin Walzer Code by Kevin http://www.codebykevin.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFqmLeEsLm8HXyq4sRAoDCAJ9qNiCJongpmH32rvLs3OTQ2wV4+ACfa0Ap YLeq1DmOIZUcVJ7hLQZ8hTU= =JQIY -----END PGP SIGNATURE----- From mstevens at etla.org Sun Jan 14 14:39:32 2007 From: mstevens at etla.org (Michael Stevens) Date: Tue Oct 9 16:39:54 2007 Subject: update zile to 2.2.25 Message-ID: <45AAB124.7000100@etla.org> Hi. I've submitted ticket 11240 to trac which updates the zile port from 2.2.24 -> 2.2.25: http://trac.macports.org/projects/macports/ticket/11240 Michael (still repeating here till I hear trac is doing something sensible with new tickets...) From eridius at macports.org Mon Jan 15 08:51:15 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts In-Reply-To: <45AA58F5.6010502@macports.org> References: <45AA58F5.6010502@macports.org> Message-ID: <5CBB3C5D-FD43-4B88-AD2E-9A0275DAEF35@macports.org> I've been looking into the feasibility of providing a port for MacFUSE (note: I'm Eridius). Unfortunately, I believe doing so will require some changes to the MacPorts codebase. The biggest problem is, at least with the official release (I haven't tested with svn HEAD yet), there's no support for a pre-deactivate hook. A pre-deactivate hook would be necessary here in order to attempt to kextunload the MacFUSE kext (I'm assuming it can be unloaded once loaded, if no FUSE filesystems are mounted, but I don't actually know that for a fact). Alternately, if the kext cannot be unloaded, a post-deactivate hook would be necessary to tell the user that they have to reboot. Alternately this could be done in a pre- deactivate hook that prompts the user if they really want to continue, knowing they'd have to reboot. Actually, offhand that's the only real problem I can think of, though I thought there were others. Maybe I'll remember others later, maybe not. In any case, the pre/post-deactivate hook is pretty important here. And actually, I want a pre-deactivate hook for another port, so it's probably worth doing regardless of MacFUSE. In any case, we also want a source distribution of MacFUSE available for this. I've filed a ticket on the MacFUSE project, so hopefully it'll happen. If not, somebody could always host one, but I'm hoping for an official one. Perhaps I'll try contacting Amit Singh later to get his input on this. If you're interested in helping out regarding getting MacFUSE into MacPorts, I'm willing to be responsible for seeing this happen, so feel free to talk to me. Best way is to contact me on IRC, I go by Eridius and I hang out on the #macports channel. Alternatively you can reach me as Aranor8 on AIM, or at . -Kevin Ballard a.k.a. Eridius On Jan 14, 2007, at 11:23 AM, Pierre Queinnec wrote: > Eridius pointed me on IRC to MacFUSE, the recently released FUSE > port to OS X. I wanted to see if there is interest in having it in > our ports. > > There is a major drawback in having kernel modules in the ports in > the fact that it's a tad easier for curious & inexperienced users > to mess up their systems. Of course, it's also a lot cooler for > some of us to just install sshfs and make it work without spending > too much time. This drawback could probably be addressed by having > a separate category (something called 'kernel' for example) where > we'd warn users that they can mess their systems up if they don't > know what they're doing. > > My first question is wether we want kexts in MacPorts at once. FUSE > would be a fine addition then, we could also add something like a > tun/tap device. If we are to just distribute the userland stuff, > it's going to be harder to get users to update their kexts to match > the userland libs versions. -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070115/64891c53/attachment.html From sal at ri.cmu.edu Mon Jan 15 09:21:10 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts In-Reply-To: <5CBB3C5D-FD43-4B88-AD2E-9A0275DAEF35@macports.org> References: <45AA58F5.6010502@macports.org> <5CBB3C5D-FD43-4B88-AD2E-9A0275DAEF35@macports.org> Message-ID: o with svn HEAD yet), there's no support for a pre-deactivate hook. A o pre-deactivate hook would be necessary here in order to attempt to o kextunload the MacFUSE kext (I'm assuming it can be unloaded once o loaded, if no FUSE filesystems are mounted, but I don't actually know o that for a fact). Alternately, if the kext cannot be unloaded, a o post-deactivate hook would be necessary to tell the user that they o have to reboot. Alternately this could be done in a pre-deactivate o hook that prompts the user if they really want to continue, knowing o they'd have to reboot. While the hooks are probably the *right* way to do this, it occurs to me that our other packages are not nearly as responsible and perhaps MacFUSE does not need to be either. That is, none of our packages shut themselves down before being removed (Apache comes to mind, but any of the daemons are examples). The "port" command generally handles installation (which includes adding hooks for activation) and deinstallation (which includes removing those hooks), but often does not include running the hooks. In some packages, the port command finishes with a message like "you may want to run X to activate this package" (the mysql port comes to mind). So, if that's the only blocker, I think you're in good shape to do just as good a job with MacFUSE as we do with other ports. Adding pre/post-activation hooks could be viewed as a separate task to improve the MP project as a whole. -- Sal smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Mon, 15 Jan 2007, Kevin Ballard wrote: o I've been looking into the feasibility of providing a port for MacFUSE (note: o I'm Eridius). Unfortunately, I believe doing so will require some changes to o the MacPorts codebase. o o The biggest problem is, at least with the official release (I haven't tested o o Actually, offhand that's the only real problem I can think of, though I o thought there were others. Maybe I'll remember others later, maybe not. In any o case, the pre/post-deactivate hook is pretty important here. And actually, I o want a pre-deactivate hook for another port, so it's probably worth doing o regardless of MacFUSE. o o In any case, we also want a source distribution of MacFUSE available for this. o I've filed a ticket on the MacFUSE project, so hopefully it'll happen. If not, o somebody could always host one, but I'm hoping for an official one. o o Perhaps I'll try contacting Amit Singh later to get his input on this. o o If you're interested in helping out regarding getting MacFUSE into MacPorts, o I'm willing to be responsible for seeing this happen, so feel free to talk to o me. Best way is to contact me on IRC, I go by Eridius and I hang out on the o #macports channel. Alternatively you can reach me as Aranor8 on AIM, or at o . o o -Kevin Ballard a.k.a. Eridius o o On Jan 14, 2007, at 11:23 AM, Pierre Queinnec wrote: o o > Eridius pointed me on IRC to MacFUSE, the recently released FUSE port to OS o > X. I wanted to see if there is interest in having it in our ports. o > o > There is a major drawback in having kernel modules in the ports in the fact o > that it's a tad easier for curious & inexperienced users to mess up their o > systems. Of course, it's also a lot cooler for some of us to just install o > sshfs and make it work without spending too much time. This drawback could o > probably be addressed by having a separate category (something called o > 'kernel' for example) where we'd warn users that they can mess their systems o > up if they don't know what they're doing. o > o > My first question is wether we want kexts in MacPorts at once. FUSE would be o > a fine addition then, we could also add something like a tun/tap device. If o > we are to just distribute the userland stuff, it's going to be harder to get o > users to update their kexts to match the userland libs versions. o o -- o Kevin Ballard o http://kevin.sb.org o eridius@macports.org o http://www.tildesoft.com o o From eridius at macports.org Mon Jan 15 13:36:46 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts In-Reply-To: References: <45AA58F5.6010502@macports.org> <5CBB3C5D-FD43-4B88-AD2E-9A0275DAEF35@macports.org> Message-ID: <18481B1B-1A35-4B36-8CED-AC4785E3F87A@macports.org> I am of the opinion that not cleanly removing a kernel extension is far worse than not shutting down apache before installing it. Especially since it's a reasonable assumption that the user knows how to shut down apache before uninstalling, but it's not so reasonable an assumption that the user knows how to unload a kernel extension before uninstalling. On Jan 15, 2007, at 12:21 PM, Salvatore Domenick Desiano wrote: > While the hooks are probably the *right* way to do this, it occurs > to me > that our other packages are not nearly as responsible and perhaps > MacFUSE does not need to be either. That is, none of our packages shut > themselves down before being removed (Apache comes to mind, but any of > the daemons are examples). > > The "port" command generally handles installation (which includes > adding > hooks for activation) and deinstallation (which includes removing > those > hooks), but often does not include running the hooks. In some > packages, > the port command finishes with a message like "you may want to run > X to > activate this package" (the mysql port comes to mind). > > So, if that's the only blocker, I think you're in good shape to do > just > as good a job with MacFUSE as we do with other ports. Adding > pre/post-activation hooks could be viewed as a separate task to > improve > the MP project as a whole. -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070115/419ad0dc/attachment.html From pmq at macports.org Tue Jan 16 08:29:35 2007 From: pmq at macports.org (Pierre Queinnec) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts In-Reply-To: <18481B1B-1A35-4B36-8CED-AC4785E3F87A@macports.org> References: <45AA58F5.6010502@macports.org> <5CBB3C5D-FD43-4B88-AD2E-9A0275DAEF35@macports.org> <18481B1B-1A35-4B36-8CED-AC4785E3F87A@macports.org> Message-ID: <45ACFD6F.4080203@macports.org> Hi Kevin, Sal, I have to say that I'd prefer MP to not load/unload the kexts for me. On wether the user knows or not how to unload the kernel extension, I think the problem should be made clear to the user when installing from the kernel category: some sort of "if you're feeling uncomfortable about this and/or don't know what you're doing, then stop". -- Pierre Kevin Ballard wrote: > I am of the opinion that not cleanly removing a kernel extension is far > worse than not shutting down apache before installing it. Especially > since it's a reasonable assumption that the user knows how to shut down > apache before uninstalling, but it's not so reasonable an assumption > that the user knows how to unload a kernel extension before uninstalling. > > On Jan 15, 2007, at 12:21 PM, Salvatore Domenick Desiano wrote: > >> While the hooks are probably the *right* way to do this, it occurs to me >> >> that our other packages are not nearly as responsible and perhaps >> >> MacFUSE does not need to be either. That is, none of our packages shut >> >> themselves down before being removed (Apache comes to mind, but any of >> >> the daemons are examples). >> >> >> The "port" command generally handles installation (which includes adding >> >> hooks for activation) and deinstallation (which includes removing those >> >> hooks), but often does not include running the hooks. In some packages, >> >> the port command finishes with a message like "you may want to run X to >> >> activate this package" (the mysql port comes to mind). >> >> >> So, if that's the only blocker, I think you're in good shape to do just >> >> as good a job with MacFUSE as we do with other ports. Adding >> >> pre/post-activation hooks could be viewed as a separate task to improve >> >> the MP project as a whole. >> > > -- > Kevin Ballard > http://kevin.sb.org > eridius@macports.org > http://www.tildesoft.com > > From eridius at macports.org Tue Jan 16 10:01:29 2007 From: eridius at macports.org (Kevin Ballard) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts In-Reply-To: <45ACFD6F.4080203@macports.org> References: <45AA58F5.6010502@macports.org> <5CBB3C5D-FD43-4B88-AD2E-9A0275DAEF35@macports.org> <18481B1B-1A35-4B36-8CED-AC4785E3F87A@macports.org> <45ACFD6F.4080203@macports.org> Message-ID: Possibly. I'd at least like to add a pre-deactivate hook that can query kextstat to see if the extension is loaded, and pop up a huge honking warning telling the user that this could be dangerous, and ask to continue? . On Jan 16, 2007, at 11:29 AM, Pierre Queinnec wrote: > I have to say that I'd prefer MP to not load/unload the kexts for > me. On wether the user knows or not how to unload the kernel > extension, I think the problem should be made clear to the user > when installing from the kernel category: some sort of "if you're > feeling uncomfortable about this and/or don't know what you're > doing, then stop". -- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070116/af6a8db7/attachment.html From mark.duling at biola.edu Tue Jan 16 21:48:22 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:54 2007 Subject: Updated portfile.7 man page - please review/commit Message-ID: Ok, so I've updated the portfile.7 manpage following James' instructions and attached it to this bug: http://trac.macosforge.org/projects/macports/ticket/4905 It adds: -startupitems.keywords -cvs.root key -svn fetch section and modifies: -changes occurrances of DarwinPorts to MacPorts -reworks dependency section to reflect new default port: style How can I get this reviewed and committed to HEAD? Mark From cedric.luthi at gmail.com Wed Jan 17 09:18:52 2007 From: cedric.luthi at gmail.com (=?ISO-8859-1?Q?C=E9dric_Luthi?=) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket #11248 commit Message-ID: Please someone with commit access, take care of this ticket ;-) http://trac.macports.org/projects/macports/ticket/11248 This will be needed for a port I plan to update also: aria2. Best regards. C?dric Luthi From ryandesign at macports.org Wed Jan 17 12:16:35 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket #11248 commit In-Reply-To: References: Message-ID: On Jan 17, 2007, at 11:18, C?dric Luthi wrote: > Please someone with commit access, take care of this ticket ;-) > http://trac.macports.org/projects/macports/ticket/11248 > > This will be needed for a port I plan to update also: aria2. Does the current maintainer agree with these changes, and is he ok with adding you as a maintainer? From mccdo at iastate.edu Thu Jan 18 15:39:48 2007 From: mccdo at iastate.edu (Doug McCorkle) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket 11232 was (Re: gmtl port file) In-Reply-To: References: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> Message-ID: <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> Can this ticket be reviewed? Thanks. http://trac.macosforge.org/projects/macports/ticket/11232 Doug On Jan 13, 2007, at 9:10 PM, Doug McCorkle wrote: > I have uploaded a new portfile that looks at the new sourceforge > server. Could this ticket be reviewed: > > http://trac.macosforge.org/projects/macports/ticket/11232 > > I did not find a way to disable looking for cppunit or boost. > > Doug > > On Jan 9, 2007, at 1:37 PM, Doug McCorkle wrote: > >> >> On Jan 8, 2007, at 4:48 PM, Mark Duling wrote: >> >>> Doug McCorkle on Wednesday, January 3, 2007 >>> at 6:48 PM >>> -0800 wrote: >>>> I have a port file for gmtl that I would like considered for >>>> addition to macports. Please let me know if the file needs to be >>>> updated in some manner to be included. Thanks for the >>>> consideration. >>> >>> Doug, >>> >>> I tried it and I have only two questions based on this: >>> >>> ------------------------------------- >>> Building GMTL Version: 0.4.12 >>> Install prefix: >>> /opt/local/var/db/dports/build/_Users_mduling_dports_math_gmtl/ >>> work/destroot/opt/local >>> checking for CppUnitDir [/usr/local/include]... >>> no >>> checking for EnablePython [False]... >>> Using Boost version 1.31 >>> checking for BoostPythonDir [/usr/local]... >>> /usr/local/include/boost/version.hpp not found. >>> Trying /usr/local/include/boost-1_31/boost/version.hpp >>> /usr/local/include/boost-1_31/boost/version.hpp not found. >>> ------------------------------------- >>> >>> 1) Should the app be compiled with boost support? If so a >>> dependency for >>> it should be added for the MP version and a switch or configure >>> patch to >>> point gmtl to the MP one. >>> 2) Or should boost support be turned off, or only off by default >>> with >>> optional support provided with a boost variant? >>> 3) If boost support is added one way or another, then unless >>> there are >>> special circumstances (and there could be because I am not in a >>> position >>> to know) then the port should not look for a non-MP boost (in / >>> usr). As >>> it is now the port will >>> 4) The same questions hold for CppUnitDir, whatever that is. >>> >> For basic development usage boost and cppunit are not needed. I >> figured after it was in use for a little while the other variants >> could be added. I talked with the developers of the library and >> they did not seem to think it was an immediate requirement to have >> the other variants available. I will see if it is possible to >> disable the boost and cppunit requirement. >> >>> After getting these issues resolved you should submit the >>> portfile as an >>> attachment to a Trac ticket, though sometimes you need to prod >>> someone to >>> commit it with a list message to get it soon. >>> >>> Mark >>> >> >> Thanks for trying it out and the feedback! >> >> Doug > > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-dev Doug McCorkle - Research Assistant Iowa State University Virtual Engineering Research Group -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070118/9c867cbc/attachment.html From cedric.luthi at gmail.com Thu Jan 18 23:05:18 2007 From: cedric.luthi at gmail.com (=?ISO-8859-1?Q?C=E9dric_Luthi?=) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket 11232 was (Re: gmtl port file) In-Reply-To: <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> References: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> Message-ID: On 19 janv. 07, at 00:39, Doug McCorkle wrote: > Can this ticket be reviewed? Thanks. > > http://trac.macosforge.org/projects/macports/ticket/11232 Just so that you know, the convention is to use master_sites sourceforge:ggt instead of master_sites http://downloads.sourceforge.net/sourceforge/ggt and use_configure no instead of configure {} Other than that, the port seems OK, but I don't have commit rights. Regards. C?dric Luthi From mark.duling at biola.edu Fri Jan 19 01:34:11 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket 11232 was (Re: gmtl port file) In-Reply-To: <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> References: <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> Message-ID: Doug McCorkle on Thursday, January 18, 2007 at 3:39 PM -0800 wrote: >Can this ticket be reviewed? Thanks. > > >[ http://trac.macosforge.org/projects/macports/ticket/11232 >]http://trac.macosforge.org/projects/macports/ticket/11232 It's committed now. Thanks for contributing. Mark From gerhard.reitmayr at gmail.com Fri Jan 19 01:36:36 2007 From: gerhard.reitmayr at gmail.com (Gerhard Reitmayr) Date: Tue Oct 9 16:39:54 2007 Subject: UPDATES for omniORB, py-omniORBpy and omniEvents Message-ID: <144a3b8b0701190136o7d4564ebn296d2fef5bc43506@mail.gmail.com> hi, I have updated the ports for omniORB and py-omniORBpy to the latest versions and fixed a problem with omniEvents. The patches are already in the trac system as tickets #11108, #11109 and #11110. here are the links to the tickets http://trac.macports.org/projects/macports/ticket/11108 http://trac.macports.org/projects/macports/ticket/11109 http://trac.macports.org/projects/macports/ticket/11110 could someone check those in? thanks a lot, Gerhard Reitmayr From ryandesign at macports.org Fri Jan 19 11:54:36 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:39:54 2007 Subject: UPDATES for omniORB, py-omniORBpy and omniEvents In-Reply-To: <144a3b8b0701190136o7d4564ebn296d2fef5bc43506@mail.gmail.com> References: <144a3b8b0701190136o7d4564ebn296d2fef5bc43506@mail.gmail.com> Message-ID: <472C594D-BF63-47C2-A2B8-6861FE12BFA1@macports.org> On Jan 19, 2007, at 03:36, Gerhard Reitmayr wrote: > I have updated the ports for omniORB and py-omniORBpy to the latest > versions and fixed a problem with omniEvents. The patches are already > in the trac system as tickets #11108, #11109 and #11110. here are > the links to the tickets > > http://trac.macports.org/projects/macports/ticket/11108 > http://trac.macports.org/projects/macports/ticket/11109 > http://trac.macports.org/projects/macports/ticket/11110 > > could someone check those in? Sure, I'll take care of it. From artemio at eresmas.net Fri Jan 19 12:42:18 2007 From: artemio at eresmas.net (Artemio Gonzalez Lopez) Date: Tue Oct 9 16:39:54 2007 Subject: problems building a local port Message-ID: <02706761-72B9-484F-8F9B-BC88E2108DBE@eresmas.net> I am trying to build locally a port (readline 5.2) by adding file:///Users/artemio/Archive/dports-dev to /opt/local/etc/ports/sources.conf, using a modification of the standard readline 5.1 portfile that I put in my local port directory (/Users/artemio/Archive/dports-dev/devel/readline). After cd'ing to said directory, I execute the command sudo port -dv build However, this fails miserably as follows: ======================================================================== ======================== DEBUG: Changing to port directory: . DEBUG: Changing to port directory: . DEBUG: Requested variant powerpc is not provided by port readline. DEBUG: Requested variant darwin is not provided by port readline. DEBUG: Requested variant macosx is not provided by port readline. DEBUG: Executing com.apple.main (readline) ---> Fetching readline DEBUG: Executing com.apple.fetch (readline) ---> Verifying checksum(s) for readline DEBUG: Executing com.apple.checksum (readline) ---> Extracting readline DEBUG: Executing com.apple.extract (readline) ---> Extracting readline-5.2.tar.gz DEBUG: setting option extract.args to /opt/local/var/db/dports/ distfiles/readline/readline-5.2.tar.gz DEBUG: Assembled command: 'cd "/opt/local/var/db/dports/build/ _Users_artemio_Archive_dports-dev_devel_readline/work" && gzip -dc / opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz | /usr/ bin/gnutar --no-same-owner -xf -' gzip: /opt/local/var/db/dports/distfiles/readline/ readline-5.2.tar.gz: No such file or directory DEBUG: Executing com.apple.patch (readline) ---> Applying patches to readline Error: Target com.apple.patch returned: couldn't change working directory to "/opt/local/var/db/dports/build/ _Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2": no such file or directory Warning: the following items did not execute (for readline): com.apple.build com.apple.patch com.apple.configure Error: Status 1 encountered during processing. ======================================================================== ======================== If I create by hand the missing directory /opt/local/var/db/dports/ build/_Users_artemio_Archive_dports-dev_devel_readline/work/ readline-5.2 here's the error I get: ======================================================================== ======================== DEBUG: Changing to port directory: . DEBUG: Changing to port directory: . DEBUG: Requested variant powerpc is not provided by port readline. DEBUG: Requested variant darwin is not provided by port readline. DEBUG: Requested variant macosx is not provided by port readline. DEBUG: Skipping completed com.apple.main (readline) DEBUG: Skipping completed com.apple.fetch (readline) DEBUG: Skipping completed com.apple.checksum (readline) DEBUG: Skipping completed com.apple.extract (readline) DEBUG: Executing com.apple.patch (readline) ---> Applying patches to readline ---> Applying /Users/artemio/Archive/dports-dev/devel/readline/files/ readline52-001 DEBUG: Assembled command: 'cd "/opt/local/var/db/dports/build/ _Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2" && patch -p0' can't find file to patch at input line 22 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- | READLINE PATCH REPORT | ===================== | |Readline-Release: 5.2 |Patch-ID: readline52-001 | |Bug-Reported-by: ebb9@byu.net |Bug-Reference-ID: <45540862.9030900@byu.net> |Bug-Reference-URL: http://lists.gnu.org/archive/html/bug-bash/ 2006-11/msg00017.html | http://lists.gnu.org/archive/html/bug-bash/ 2006-11/msg00016.html | |Bug-Description: | |In some cases, code that is intended to be used in the presence of multibyte |characters is called when no such characters are present, leading to incorrect |display position calculations and incorrect redisplay. | |Patch: | |*** ../readline-5.2/display.c Thu Sep 14 14:20:12 2006 |--- display.c Mon Nov 13 17:55:57 2006 -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored Error: Target com.apple.patch returned: shell command "cd "/opt/local/ var/db/dports/build/_Users_artemio_Archive_dports-dev_devel_readline/ work/readline-5.2" && patch -p0 < "/Users/artemio/Archive/dports-dev/ devel/readline/files/readline52-001"" returned error 1 Command output: can't find file to patch at input line 22 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- | READLINE PATCH REPORT | ===================== ... -------------------------- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored Warning: the following items did not execute (for readline): com.apple.build com.apple.patch com.apple.configure Error: Status 1 encountered during processing. ======================================================================== ======================== Simpler commands like sudo port -dv fetch are totally ignored: DEBUG: Changing to port directory: . DEBUG: Changing to port directory: . DEBUG: Requested variant powerpc is not provided by port readline. DEBUG: Requested variant darwin is not provided by port readline. DEBUG: Requested variant macosx is not provided by port readline. DEBUG: Skipping completed com.apple.main (readline) DEBUG: Skipping completed com.apple.fetch (readline) I wonder if I'm missing something really obvious here (I used to build my local ports with a previous version of darwinports, and never had such a problem). Any suggestions/pointers? Cheers, Artemio Artemio Gonzalez-Lopez artemio@eresmas.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070119/6da12030/attachment.html From jkh at brierdr.com Fri Jan 19 12:47:43 2007 From: jkh at brierdr.com (Jordan K. Hubbard) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket 11232 was (Re: gmtl port file) In-Reply-To: References: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> Message-ID: On Jan 18, 2007, at 11:05 PM, C?dric Luthi wrote: > Other than that, the port seems OK, but I don't have commit rights. Would you like some? We can always use people who are motivated enough to go through TRAC and commit stuff! :-) - Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-dev/attachments/20070119/fa0de80f/attachment.html From mccdo at iastate.edu Fri Jan 19 12:50:00 2007 From: mccdo at iastate.edu (Doug McCorkle) Date: Tue Oct 9 16:39:54 2007 Subject: Ticket 11232 was (Re: gmtl port file) In-Reply-To: References: <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> Message-ID: <18343.147.216.67.106.1169239800.squirrel@mail.eng.iastate.edu> > Doug McCorkle on Thursday, January 18, 2007 at 3:39 PM > -0800 wrote: >>Can this ticket be reviewed? Thanks. >> >> >>[ http://trac.macosforge.org/projects/macports/ticket/11232 >>]http://trac.macosforge.org/projects/macports/ticket/11232 > > It's committed now. Thanks for contributing. > > Mark > > Thanks! Doug From mark.duling at biola.edu Fri Jan 19 16:19:40 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:54 2007 Subject: problems building a local port In-Reply-To: <02706761-72B9-484F-8F9B-BC88E2108DBE@eresmas.net> References: <02706761-72B9-484F-8F9B-BC88E2108DBE@eresmas.net> Message-ID: Artemio Gonzalez Lopez on Friday, January 19, 2007 at 12:42 PM -0800 wrote: >I am trying to build locally a port (readline 5.2) by adding > > >[ file:///Users/artemio/Archive/dports-dev >]file:///Users/artemio/Archive/dports-dev > > >to /opt/local/etc/ports/sources.conf, using a modification of the >standard readline 5.1 portfile that I put in my local port directory >(/Users/artemio/Archive/dports-dev/devel/readline). After cd'ing to said >directory, I execute the command > > >sudo port -dv build > > >However, this fails miserably as follows: > > >================================================================================================ >DEBUG: Changing to port directory: . >DEBUG: Changing to port directory: . >DEBUG: Requested variant powerpc is not provided by port readline. >DEBUG: Requested variant darwin is not provided by port readline. >DEBUG: Requested variant macosx is not provided by port readline. >DEBUG: Executing com.apple.main (readline) >---> Fetching readline >DEBUG: Executing com.apple.fetch (readline) >---> Verifying checksum(s) for readline >DEBUG: Executing com.apple.checksum (readline) >---> Extracting readline >DEBUG: Executing com.apple.extract (readline) >---> Extracting readline-5.2.tar.gz >DEBUG: setting option extract.args to >/opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz >DEBUG: Assembled command: 'cd >"/opt/local/var/db/dports/build/_Users_artemio_Archive_dports-dev_devel_readline/work" >&& gzip -dc >/opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz | >/usr/bin/gnutar --no-same-owner -xf -' >gzip: /opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz: No >such file or directory >DEBUG: Executing com.apple.patch (readline) >---> Applying patches to readline >Error: Target com.apple.patch returned: couldn't change working directory >to >"/opt/local/var/db/dports/build/_Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2": >no such file or directory >Warning: the following items did not execute (for readline): >com.apple.build com.apple.patch com.apple.configure >Error: Status 1 encountered during processing. >================================================================================================ > > >If I create by hand the missing directory >/opt/local/var/db/dports/build/_Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2 >here's the error I get: > > >================================================================================================ >DEBUG: Changing to port directory: . >DEBUG: Changing to port directory: . >DEBUG: Requested variant powerpc is not provided by port readline. >DEBUG: Requested variant darwin is not provided by port readline. >DEBUG: Requested variant macosx is not provided by port readline. >DEBUG: Skipping completed com.apple.main (readline) >DEBUG: Skipping completed com.apple.fetch (readline) >DEBUG: Skipping completed com.apple.checksum (readline) >DEBUG: Skipping completed com.apple.extract (readline) >DEBUG: Executing com.apple.patch (readline) >---> Applying patches to readline >---> Applying >/Users/artemio/Archive/dports-dev/devel/readline/files/readline52-001 >DEBUG: Assembled command: 'cd >"/opt/local/var/db/dports/build/_Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2" >&& patch -p0' >can't find file to patch at input line 22 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >| READLINE PATCH REPORT >| ===================== >| >|Readline-Release: 5.2 >|Patch-ID: readline52-001 >| >|Bug-Reported-by: [ mailto:ebb9@byu.net ]ebb9@byu.net >|Bug-Reference-ID: <[ mailto:45540862.9030900@byu.net >]45540862.9030900@byu.net> >|Bug-Reference-URL: [ >http://lists.gnu.org/archive/html/bug-bash/2006-11/msg00017.html >]http://lists.gnu.org/archive/html/bug-bash/2006-11/msg00017.html >| [ >http://lists.gnu.org/archive/html/bug-bash/2006-11/msg00016.html >]http://lists.gnu.org/archive/html/bug-bash/2006-11/msg00016.html >| >|Bug-Description: >| >|In some cases, code that is intended to be used in the presence of >multibyte >|characters is called when no such characters are present, leading to >incorrect >|display position calculations and incorrect redisplay. >| >|Patch: >| >|*** ../readline-5.2/display.c Thu Sep 14 14:20:12 2006 >|--- display.c Mon Nov 13 17:55:57 2006 >-------------------------- >File to patch: >Skip this patch? [y] >Skipping patch. >1 out of 1 hunk ignored >Error: Target com.apple.patch returned: shell command "cd >"/opt/local/var/db/dports/build/_Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2" >&& patch -p0 < >"/Users/artemio/Archive/dports-dev/devel/readline/files/readline52-001"" >returned error 1 >Command output: can't find file to patch at input line 22 >Perhaps you used the wrong -p or --strip option? >The text leading up to this was: >-------------------------- >| READLINE PATCH REPORT >| ===================== >... >-------------------------- >File to patch: >Skip this patch? [y] >Skipping patch. >1 out of 1 hunk ignored > > >Warning: the following items did not execute (for readline): >com.apple.build com.apple.patch com.apple.configure >Error: Status 1 encountered during processing. >================================================================================================ > > >Simpler commands like > > >sudo port -dv fetch > > >are totally ignored: > > > > >DEBUG: Changing to port directory: . >DEBUG: Changing to port directory: . >DEBUG: Requested variant powerpc is not provided by port readline. >DEBUG: Requested variant darwin is not provided by port readline. >DEBUG: Requested variant macosx is not provided by port readline. >DEBUG: Skipping completed com.apple.main (readline) >DEBUG: Skipping completed com.apple.fetch (readline) > > > > >I wonder if I'm missing something really obvious here (I used to build my >local ports with a previous version of darwinports, and never had such a >problem). Any suggestions/pointers? If readline 5.2 doesn't extract into readline-5.2, you'll need to set the worksrcdir manually. The default MacPorts look for is is ${name}-${version}, but perhaps it something else. See what the actual directory name is and set it. If the directory name (work/readline...) is just "readline", then your statement would look like this: worksrcdir readline or better still worksrcdir ${name} Mark From adam at miraculo.com Fri Jan 19 17:30:10 2007 From: adam at miraculo.com (adam salter) Date: Tue Oct 9 16:39:54 2007 Subject: Kernel extensions in MacPorts Message-ID: Hi guys, I was investigating why there is no MacPort for MacFUSE, found this discussion through GMane, and just wanted to throw my 2 cents in. I don't know a lot about the kernel extension loading/unloading, but I don't see why the source install is such a problem. Ports has a way to set the install variant... couldn't we have an install for those with subversion installed, and those without? At the moment it could bomb out with a message like "no source file found - you can install subversion and install this package with 'port install macfuse variant:svn'" Thanks in advance, Adam From mark.duling at biola.edu Fri Jan 19 18:10:48 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:55 2007 Subject: case sensitivity issue I didn't know about Message-ID: I was installing unixODBC and I noticed after an uninstall it was leaving files behind even though it was removing itself from the port registry. But I notice that it does remove all files if I uninstall using the case sensitive name. Is that a known issue? I knew about some case sensitivity issues but not one where a command partially works, which is even more confusing than when 'port contents foo' shows nothing after 'port install foo' when foo is a port named "Foo". Mark From roederja at student.ethz.ch Sat Jan 20 04:38:28 2007 From: roederja at student.ethz.ch (=?UTF-8?B?SmFubiBSw7ZkZXI=?=) Date: Tue Oct 9 16:39:55 2007 Subject: Naming of postgresql & related In-Reply-To: <1107CBE6-1374-4541-A1E6-CE4D1107E199@geeklair.net> References: <3F37E552-5086-4B0B-8197-02AAF21F8300@macports.org> <1107CBE6-1374-4541-A1E6-CE4D1107E199@geeklair.net> Message-ID: Hi, this issue just came to my attention again: On the postgreSQl website the following versions are available: - 8.2.1 - 8.1.6 - 8.0.10 - 7.4.15 In macports the following ports are available: postgresql databases/postgresql 7.4.12 postgresql7 databases/postgresql7 7.4.13 postgresql8 databases/postgresql8 8.1.3 postgresql81 databases/postgresql81 8.1.5 postgresql82 databases/postgresql82 8.2.1 It seems to me that the posgresql8 port is installing the wrong version - should be 8.0.10 instead of 8.1.3 , the posgresql port should be removed, postgresql7 and psogresql81 are slightly out of date. So I think the postgresql port (with no version) should be deleted, and the others should be updated. What do you think ? Jann Daniel J. Luke wrote: > On Nov 4, 2006, at 6:39 AM, Jyrki Wahlstedt wrote: >> I just wonder about naming postgresql, some other ports could have the >> same. Currently postgresql installs v.7.4.12. Then we have postgresql7 >> (v.7.4.13), postgresql8 (v.8.1.3) and postgresql81 (v.8.1.4). This is >> a mess. I think postgresql should always be the latest, then we could, >> if we want, to have version-specific ports (~7, ~8, ~81). How about this? > > This was changed because people do 'port upgrade' and wanted things to > work. And because of your point below, the easiest thing is to just have > version-specific ports (and let the user handle the file format > incompatible upgrades themselves). > > I believe the 'postgresql' port was deprecated when the decision was > made and that it was intended for it to be removed (but I could remember > incorrectly). > >> The related thing comes from the fact that the database formats >> between point versions of postgresql are not compatible (8.0->8.1). Is >> there a way to make sure that database is dumped before upgrade. > > That is probably possible, but I don't know if it makes sense to attempt > this (for instance, I have a database that would take days to dump that > contains data that I'm happy to toss when I want to do an upgrade, but > the upgrade step can't know that). > > Also, 'upgrade' isn't really a normal target, so it would be a hack in > the portfile to attempt to do this. > >> Could one ask a question from the user and wait for an answer (to >> confirm the operation)? > > No. Ports don't prompt for things - this would break unattended > (scripted) operation. > > -- > Daniel J. Luke > +========================================================+ > | *---------------- dluke@geeklair.net > ----------------* | > | *-------------- http://www.geeklair.net -------------* | > +========================================================+ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > +========================================================+ > > > > ------------------------------------------------------------------------ > > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-dev From rhwood at mac.com Sat Jan 20 05:52:44 2007 From: rhwood at mac.com (Randall Wood) Date: Tue Oct 9 16:39:55 2007 Subject: D-Bus & GNOME upgrades Message-ID: <67C04485-B819-42C3-BEDF-064B466C110B@mac.com> This weekend I submitted a large number of D-Bus and GNOME upgrades to MacPorts, and will be submitting more in the coming days. D-Bus (port dbus): D-Bus has been upgraded from 0.61 to 1.0.2 and port dbus-glib has been added at version 0.72. This is a significant upgrade to D-Bus and breaks compatibility with version 0.61. All ports that depend on port:dbus have to be rebuilt to run. GNOME: About 3 dozen GNOME ports have been identified as having or requiring a dependency on D-Bus (I tested for apps and libs that linked against dbus-glib). The current stable version of about a dozen were known to be dependent on D-Bus 1.0.+ and have been upgraded to the latest stable versions. Another dozen or so have been revised to explicitly depend on port:dbus-glib and the revision tag has been incremented to force a rebuild when dbus is upgraded on user's systems. A few more are having one or more other build issues that need to be worked out before being upgraded. These changes should bring almost every GNOME port currently shipping in MacPorts up to GNOME 2.16.x specs, and the master GNOME port has been upgraded as well to reflect this. Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From rhwood at mac.com Sat Jan 20 06:35:07 2007 From: rhwood at mac.com (Randall Wood) Date: Tue Oct 9 16:39:55 2007 Subject: Naming of postgresql & related In-Reply-To: References: <3F37E552-5086-4B0B-8197-02AAF21F8300@macports.org> <1107CBE6-1374-4541-A1E6-CE4D1107E199@geeklair.net> Message-ID: I would not remove port:postgresql, but make it an informative port that installs nothing, instead just spewing out an explanation of the other postgresql ports. I would also replace port:postgresql8 with a port:postgresql80 that carries the 8.0.x postgresql and otherwise just keep the other postgresqlx ports current. On 20 Jan 2007, at 07:38, Jann R?der wrote: > Hi, > this issue just came to my attention again: On the postgreSQl website > the following versions are available: > - 8.2.1 > - 8.1.6 > - 8.0.10 > - 7.4.15 > > In macports the following ports are available: > > postgresql databases/postgresql 7.4.12 > postgresql7 databases/postgresql7 7.4.13 > postgresql8 databases/postgresql8 8.1.3 > postgresql81 databases/postgresql81 8.1.5 > postgresql82 databases/postgresql82 8.2.1 > > It seems to me that the posgresql8 port is installing the wrong > version > - should be 8.0.10 instead of 8.1.3 , the posgresql port should be > removed, postgresql7 and psogresql81 are slightly out of date. > > So I think the postgresql port (with no version) should be deleted, > and > the others should be updated. > > What do you think ? > > Jann > > Daniel J. Luke wrote: >> On Nov 4, 2006, at 6:39 AM, Jyrki Wahlstedt wrote: >>> I just wonder about naming postgresql, some other ports could >>> have the >>> same. Currently postgresql installs v.7.4.12. Then we have >>> postgresql7 >>> (v.7.4.13), postgresql8 (v.8.1.3) and postgresql81 (v.8.1.4). >>> This is >>> a mess. I think postgresql should always be the latest, then we >>> could, >>> if we want, to have version-specific ports (~7, ~8, ~81). How >>> about this? >> >> This was changed because people do 'port upgrade' and wanted >> things to >> work. And because of your point below, the easiest thing is to >> just have >> version-specific ports (and let the user handle the file format >> incompatible upgrades themselves). >> >> I believe the 'postgresql' port was deprecated when the decision was >> made and that it was intended for it to be removed (but I could >> remember >> incorrectly). >> >>> The related thing comes from the fact that the database formats >>> between point versions of postgresql are not compatible (8.0- >>> >8.1). Is >>> there a way to make sure that database is dumped before upgrade. >> >> That is probably possible, but I don't know if it makes sense to >> attempt >> this (for instance, I have a database that would take days to dump >> that >> contains data that I'm happy to toss when I want to do an upgrade, >> but >> the upgrade step can't know that). >> >> Also, 'upgrade' isn't really a normal target, so it would be a >> hack in >> the portfile to attempt to do this. >> >>> Could one ask a question from the user and wait for an answer (to >>> confirm the operation)? >> >> No. Ports don't prompt for things - this would break unattended >> (scripted) operation. >> >> -- >> Daniel J. Luke >> +========================================================+ >> | *---------------- dluke@geeklair.net >> ----------------* | >> | *-------------- http://www.geeklair.net -------------* | >> +========================================================+ >> | Opinions expressed are mine and do not necessarily | >> | reflect the opinions of my employer. | >> +========================================================+ >> >> >> >> --------------------------------------------------------------------- >> --- >> >> _______________________________________________ >> 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 Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From artemio at eresmas.net Sat Jan 20 11:26:37 2007 From: artemio at eresmas.net (Artemio Gonzalez Lopez) Date: Tue Oct 9 16:39:55 2007 Subject: problems building a local port In-Reply-To: References: <02706761-72B9-484F-8F9B-BC88E2108DBE@eresmas.net> Message-ID: <2CAFD9C1-828F-44ED-A3EB-05E4852B4ED5@eresmas.net> On Jan 20, 2007, at 1:19 AM, Mark Duling wrote: > Artemio Gonzalez Lopez on Friday, January 19, > 2007 > at 12:42 PM -0800 wrote: >> I am trying to build locally a port (readline 5.2) by adding >> >> [ file:///Users/artemio/Archive/dports-dev >> ]file:///Users/artemio/Archive/dports-dev >> >> to /opt/local/etc/ports/sources.conf, using a modification of the >> standard readline 5.1 portfile that I put in my local port directory >> (/Users/artemio/Archive/dports-dev/devel/readline). After cd'ing >> to said >> directory, I execute the command >> >> sudo port -dv build >> >> However, this fails miserably as follows: >> >> >> ===================================================================== >> =========================== >> DEBUG: Changing to port directory: . >> DEBUG: Changing to port directory: . >> DEBUG: Requested variant powerpc is not provided by port readline. >> DEBUG: Requested variant darwin is not provided by port readline. >> DEBUG: Requested variant macosx is not provided by port readline. >> DEBUG: Executing com.apple.main (readline) >> ---> Fetching readline >> DEBUG: Executing com.apple.fetch (readline) >> ---> Verifying checksum(s) for readline >> DEBUG: Executing com.apple.checksum (readline) >> ---> Extracting readline >> DEBUG: Executing com.apple.extract (readline) >> ---> Extracting readline-5.2.tar.gz >> DEBUG: setting option extract.args to >> /opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz >> DEBUG: Assembled command: 'cd >> "/opt/local/var/db/dports/build/_Users_artemio_Archive_dports- >> dev_devel_readline/work" >> && gzip -dc >> /opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz | >> /usr/bin/gnutar --no-same-owner -xf -' >> gzip: /opt/local/var/db/dports/distfiles/readline/ >> readline-5.2.tar.gz: No >> such file or directory >> DEBUG: Executing com.apple.patch (readline) >> ---> Applying patches to readline >> Error: Target com.apple.patch returned: couldn't change working >> directory >> to >> "/opt/local/var/db/dports/build/_Users_artemio_Archive_dports- >> dev_devel_readline/work/readline-5.2": >> no such file or directory >> Warning: the following items did not execute (for readline): >> com.apple.build com.apple.patch com.apple.configure >> Error: Status 1 encountered during processing. >> ===================================================================== >> =========================== > > If readline 5.2 doesn't extract into readline-5.2, you'll need to > set the > worksrcdir manually. The default MacPorts look for is is > ${name}-${version}, but perhaps it something else. See what the > actual > directory name is and set it. If the directory name (work/ > readline...) is > just "readline", then your statement would look like this: > > worksrcdir readline > > or better still > > worksrcdir ${name} > > Mark > Mark, Thanks for your message. From the output above, it seems that the directory name is actually work/readline-5.2, so I set worksrcdir ${name}-${version} in the modified Portfile. This doesn't work either: imac-g5:~/Archive/dports-dev/devel/readline artemio$ sudo port -dv build Password: DEBUG: Changing to port directory: . DEBUG: Changing to port directory: . DEBUG: Requested variant powerpc is not provided by port readline. DEBUG: Requested variant darwin is not provided by port readline. DEBUG: Requested variant macosx is not provided by port readline. Portfile changed since last build; discarding previous state. DEBUG: Executing com.apple.main (readline) ---> Fetching readline DEBUG: Executing com.apple.fetch (readline) ---> Verifying checksum(s) for readline DEBUG: Executing com.apple.checksum (readline) ---> Extracting readline DEBUG: Executing com.apple.extract (readline) ---> Extracting readline-5.2.tar.gz DEBUG: setting option extract.args to /opt/local/var/db/dports/ distfiles/readline/readline-5.2.tar.gz DEBUG: Assembled command: 'cd "/opt/local/var/db/dports/build/ _Users_artemio_Archive_dports-dev_devel_readline/work" && gzip -dc / opt/local/var/db/dports/distfiles/readline/readline-5.2.tar.gz | /usr/ bin/gnutar --no-same-owner -xf -' gzip: /opt/local/var/db/dports/distfiles/readline/ readline-5.2.tar.gz: No such file or directory DEBUG: Executing com.apple.patch (readline) ---> Applying patches to readline Error: Target com.apple.patch returned: couldn't change working directory to "/opt/local/var/db/dports/build/ _Users_artemio_Archive_dports-dev_devel_readline/work/readline-5.2": no such file or directory Warning: the following items did not execute (for readline): com.apple.build com.apple.patch com.apple.configure Error: Status 1 encountered during processing. It also looks like port is looking for readline-5.2.tar.gz in opt/ local/var/db/dports/distfiles/readline/ and not finding it, reporting an error instead of fetching it. I really have the impression that perhaps I am not following the right procedure for building a port in a local directory. Any suggestions? Thanks, Artemio From sal at ri.cmu.edu Sat Jan 20 12:27:35 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:55 2007 Subject: Naming of postgresql & related In-Reply-To: References: <3F37E552-5086-4B0B-8197-02AAF21F8300@macports.org> <1107CBE6-1374-4541-A1E6-CE4D1107E199@geeklair.net> Message-ID: We've had a couple of longish discussions about how to handle ports with multiple current versions. I think that mysql was the last such debate. Maybe we should have a "policy" about this. I'm thinking something like - one port for each version that the project, itself, deems to be in current service, each with the version number in it (in this case, postgresql74 postgresql80 postgresql81 postgresql82) - one default, empty port which simply has a dependency on the most recent version (in this case, postgresql, which depends on postgresql82). This way, if people do it blindly (postgresql), they get the most recent. If people write ports that need postgresql, they automatically get a dependency on the most recent version. If a writer of another port (say, port "A") discovers that A only works with one specific version of postgresql, they can use one of postgresql{74,81,82} as a dependency. In this case, it would be that port writer's responsibility to update the Portfile for A to the most recent workable dependency (since automatic upgrades have become a non-starter for A). Incidentally, I only think this should be used for specific ports where more than one major version is constantly in active use (apache, mysql, postgresql come to mind). In other cases a "beta" variant might be a better approach. Thoughts? -- Sal smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sat, 20 Jan 2007, Randall Wood wrote: o I would not remove port:postgresql, but make it an informative port that o installs nothing, instead just spewing out an explanation of the other o postgresql ports. o o I would also replace port:postgresql8 with a port:postgresql80 that carries o the 8.0.x postgresql o and otherwise just keep the other postgresqlx ports current. o o On 20 Jan 2007, at 07:38, Jann R?der wrote: o o > Hi, o > this issue just came to my attention again: On the postgreSQl website o > the following versions are available: o > - 8.2.1 o > - 8.1.6 o > - 8.0.10 o > - 7.4.15 o > o > In macports the following ports are available: o > o > postgresql databases/postgresql 7.4.12 o > postgresql7 databases/postgresql7 7.4.13 o > postgresql8 databases/postgresql8 8.1.3 o > postgresql81 databases/postgresql81 8.1.5 o > postgresql82 databases/postgresql82 8.2.1 o > o > It seems to me that the posgresql8 port is installing the wrong version o > - should be 8.0.10 instead of 8.1.3 , the posgresql port should be o > removed, postgresql7 and psogresql81 are slightly out of date. o > o > So I think the postgresql port (with no version) should be deleted, and o > the others should be updated. o > o > What do you think ? o > o > Jann o > o > Daniel J. Luke wrote: o > > On Nov 4, 2006, at 6:39 AM, Jyrki Wahlstedt wrote: o > > > I just wonder about naming postgresql, some other ports could have the o > > > same. Currently postgresql installs v.7.4.12. Then we have postgresql7 o > > > (v.7.4.13), postgresql8 (v.8.1.3) and postgresql81 (v.8.1.4). This is o > > > a mess. I think postgresql should always be the latest, then we could, o > > > if we want, to have version-specific ports (~7, ~8, ~81). How about o > > > this? o > > o > > This was changed because people do 'port upgrade' and wanted things to o > > work. And because of your point below, the easiest thing is to just have o > > version-specific ports (and let the user handle the file format o > > incompatible upgrades themselves). o > > o > > I believe the 'postgresql' port was deprecated when the decision was o > > made and that it was intended for it to be removed (but I could remember o > > incorrectly). o > > o > > > The related thing comes from the fact that the database formats o > > > between point versions of postgresql are not compatible (8.0->8.1). Is o > > > there a way to make sure that database is dumped before upgrade. o > > o > > That is probably possible, but I don't know if it makes sense to attempt o > > this (for instance, I have a database that would take days to dump that o > > contains data that I'm happy to toss when I want to do an upgrade, but o > > the upgrade step can't know that). o > > o > > Also, 'upgrade' isn't really a normal target, so it would be a hack in o > > the portfile to attempt to do this. o > > o > > > Could one ask a question from the user and wait for an answer (to o > > > confirm the operation)? o > > o > > No. Ports don't prompt for things - this would break unattended o > > (scripted) operation. o > > o > > -- o > > Daniel J. Luke o > > +========================================================+ o > > | *---------------- dluke@geeklair.net o > > ----------------* | o > > | *-------------- http://www.geeklair.net -------------* | o > > +========================================================+ o > > | Opinions expressed are mine and do not necessarily | o > > | reflect the opinions of my employer. | o > > +========================================================+ o > > o > > o > > o > > ------------------------------------------------------------------------ o > > o > > _______________________________________________ o > > macports-dev mailing list o > > macports-dev@lists.macosforge.org o > > http://lists.macosforge.org/mailman/listinfo/macports-dev o > o > _______________________________________________ o > macports-dev mailing list o > macports-dev@lists.macosforge.org o > http://lists.macosforge.org/mailman/listinfo/macports-dev o o o Randall Wood o rhwood@mac.com o o "The rules are simple: The ball is round. The game lasts 90 minutes. All the o rest is just philosophy." o o o _______________________________________________ o macports-dev mailing list o macports-dev@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-dev o From olaf at foellinger.de Sat Jan 20 13:58:30 2007 From: olaf at foellinger.de (Olaf Foellinger) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files Message-ID: <20070120215830.GA8194@merlin.in-berlin.de> Hi, I'm looking for an example of a port that only extracts and installs some files. I want to add cleanscore which consists of a perl script and some documentation but nothing to compile. Please tell me the name of a port which has a similar source. Gruss Olaf From sal at ri.cmu.edu Sat Jan 20 14:17:22 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files In-Reply-To: <20070120215830.GA8194@merlin.in-berlin.de> References: <20070120215830.GA8194@merlin.in-berlin.de> Message-ID: Look at the arc port in the archivers group (starts w/ "ar", first one I found). -- Sal smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sat, 20 Jan 2007, Olaf Foellinger wrote: o Hi, o o I'm looking for an example of a port that only extracts and installs o some files. I want to add cleanscore which consists of a perl script and o some documentation but nothing to compile. o o Please tell me the name of a port which has a similar source. o o Gruss Olaf o _______________________________________________ o macports-dev mailing list o macports-dev@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-dev o o From mark.duling at biola.edu Sat Jan 20 14:20:25 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files In-Reply-To: <20070120215830.GA8194@merlin.in-berlin.de> References: <20070120215830.GA8194@merlin.in-berlin.de> Message-ID: Olaf Foellinger on Saturday, January 20, 2007 at 1:58 PM -0800 wrote: >I'm looking for an example of a port that only extracts and installs >some files. I want to add cleanscore which consists of a perl script and >some documentation but nothing to compile. > >Please tell me the name of a port which has a similar source. Gruss, These MacPorts: base nedi are two examples of mine. Also, if there are few directories to copy and no nested directories, it just takes two statements per path in a destroot phase. xintall -d -m 755 ${worksrcpath}/path1 ${destroot}/path1 eval xintall -m 755 [glob ${worksrcpath}/path1/*.pl] ${destroot}/path1 I think I made the nedi use gnutar because I thought maybe mimicking what happens automatically in the extract phase would be good. But I don't know, recently learned that someone got this: -------------------- ---> Staging nedi into destroot Error: Target com.apple.destroot returned: shell command "cd /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_net_nedi/work/destroot/opt/local/share && gzip -dc /opt/local/var/db/dports/distfiles/nedi/nedi-1.0.w-rc3.tgz | /usr/bin/gnutar --no-same-owner -xf -" returned error 2 Command output: /usr/bin/gnutar: unrecognized option `--no-same-owner' Try `/usr/bin/gnutar --help' for more information. gzip: stdout: Broken pipe ---------------------- I've never seen this before. Does anyone know what would cause this error on OS X? Mark From sal at ri.cmu.edu Sat Jan 20 14:25:15 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files In-Reply-To: References: <20070120215830.GA8194@merlin.in-berlin.de> Message-ID: o I've never seen this before. Does anyone know what would cause this error o on OS X? On Tiger, at least, gnutar and tar are the same program and don't actually seem to be gnutar (they lack many of the options). So, if someone has the gnutar port installed and ahead of /usr/bin, the port is good to go. If not, you'll get the error you saw. -- Sal smile. -------------- Salvatore Domenick Desiano Doctoral Candidate Robotics Institute Carnegie Mellon University On Sat, 20 Jan 2007, Mark Duling wrote: o Olaf Foellinger on Saturday, January 20, 2007 at 1:58 o PM -0800 wrote: o >I'm looking for an example of a port that only extracts and installs o >some files. I want to add cleanscore which consists of a perl script and o >some documentation but nothing to compile. o > o >Please tell me the name of a port which has a similar source. o o Gruss, o o These MacPorts: o o base o nedi o o are two examples of mine. Also, if there are few directories to copy and o no nested directories, it just takes two statements per path in a destroot o phase. o o xintall -d -m 755 ${worksrcpath}/path1 ${destroot}/path1 o eval xintall -m 755 [glob ${worksrcpath}/path1/*.pl] ${destroot}/path1 o o I think I made the nedi use gnutar because I thought maybe mimicking what o happens automatically in the extract phase would be good. But I don't o know, recently learned that someone got this: o o -------------------- o ---> Staging nedi into destroot o Error: Target com.apple.destroot returned: shell command "cd o /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_net_nedi/work/destroot/opt/local/share o && gzip -dc /opt/local/var/db/dports/distfiles/nedi/nedi-1.0.w-rc3.tgz | o /usr/bin/gnutar --no-same-owner -xf -" returned error 2 o Command output: /usr/bin/gnutar: unrecognized option `--no-same-owner' o Try `/usr/bin/gnutar --help' for more information. o o gzip: stdout: Broken pipe o ---------------------- o o o Mark o o _______________________________________________ o macports-dev mailing list o macports-dev@lists.macosforge.org o http://lists.macosforge.org/mailman/listinfo/macports-dev o o From dluke at geeklair.net Sat Jan 20 15:34:41 2007 From: dluke at geeklair.net (Daniel J. Luke) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files In-Reply-To: References: <20070120215830.GA8194@merlin.in-berlin.de> Message-ID: On Jan 20, 2007, at 5:25 PM, Salvatore Domenick Desiano wrote: > o I've never seen this before. Does anyone know what would cause > this error > o on OS X? > > On Tiger, at least, gnutar and tar are the same program and don't > actually seem to be gnutar (they lack many of the options). On Tiger (10.4) tar is gnutar is GNU tar 1.14 (and supports --no-same- owner) On previous versions of Mac OS X (I'm not sure if it was 10.3 and before or 10.2 and before) tar was bsd tar and there was also gnutar present. > So, if > someone has the gnutar port installed and ahead of /usr/bin, the > port is > good to go. If not, you'll get the error you saw. --no-same-owner isn't available everywhere (and macports base actually checks to see if it's available when building from source). If a port really needs it when it is available, the portfile could probably look at tar_command from port_autoconf.tcl -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20070120/08c7c633/PGP.bin From sal at ri.cmu.edu Sat Jan 20 15:48:57 2007 From: sal at ri.cmu.edu (Salvatore Domenick Desiano) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files In-Reply-To: References: <20070120215830.GA8194@merlin.in-berlin.de> Message-ID: o > On Tiger, at least, gnutar and tar are the same program and don't o > actually seem to be gnutar (they lack many of the options). o o On Tiger (10.4) tar is gnutar is GNU tar 1.14 (and supports --no-same-owner) Fascinating. Upon further investigation, the *man pages* for tar on Tiger are not gnutar, even though the binaries are. -- Sal smile. From mark.duling at biola.edu Sat Jan 20 18:01:43 2007 From: mark.duling at biola.edu (Mark Duling) Date: Tue Oct 9 16:39:55 2007 Subject: seeking example for port who moves only some files In-Reply-To: References: Message-ID: "Daniel J. Luke" on Saturday, January 20, 2007 at 3:34 PM -0800 wrote: > >--no-same-owner isn't available everywhere (and macports base >actually checks to see if it's available when building from source). > >If a port really needs it when it is available, the portfile could >probably look at tar_command from port_autoconf.tcl Ah I see. I'll check this out and rework the nedi port so it will work on earlier systems. Thanks Daniel and Salvatore for the detailed information! Mark From sbranzo at gmail.com Sun Jan 21 07:40:12 2007 From: sbranzo at gmail.com (Sbranzo) Date: Tue Oct 9 16:39:55 2007 Subject: Extraction command and fink conflict Message-ID: <20070121154012.GA26945@sbranzo.local> I used to have fink installed, because I needed a working postfix. Now postfix is ok under macports so I want to remove fink. If I move /sw to /sw-old, for example, here's what I have If I try to install some new program in macports: sudo port -vc install unix2dos [...] ---> Extracting unix2dos-2.2.src.tar.gz sh: line 1: /sw/bin/gtar: No such file or directory gzip: stdout: Broken pipe Error: Target com.apple.extract returned: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_textproc_unix2dos/work" && gzip -dc /opt/local/var/db/dports/distfiles/unix2dos/unix2dos-2.2.src.tar.gz | /sw/bin/gtar --no-same-owner -xf -" returned error 127 Command output: sh: line 1: /sw/bin/gtar: No such file or directory So I tought installing gnutar under macports could be of any help, and mv'ed back /sw/ from /sw-old. Installation was smooth, because port used /sw/bin/gtar to unpack tarballs. Then I moved /sw to /sw-old, expecting macports will use the new gnutar, but the problem is similar: sudo port -vc install unix2dos [...] ---> Extracting unix2dos-2.2.src.tar.gz sh: line 1: /sw/bin/gnutar: No such file or directory gzip: stdout: Broken pipe Error: Target com.apple.extract returned: shell command "cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_textproc_unix2dos/work" && gzip -dc /opt/local/var/db/dports/distfiles/unix2dos/unix2dos-2.2.src.tar.gz | /sw/bin/gnutar --no-same-owner -xf -" returned error 127 Command output: sh: line 1: /sw/bin/gnutar: No such file or directory Now it looks for /sw/bin/gnutar, the name has changed (it was gtar before). Why does port look for commands in /sw/bin? I used to have /sw/{bin,sbin} in my path (and in root's path too), but now I removed all the references. Thanks in advance, Gufo From dluke at geeklair.net Sun Jan 21 09:02:25 2007 From: dluke at geeklair.net (Daniel J. Luke) Date: Tue Oct 9 16:39:55 2007 Subject: Extraction command and fink conflict In-Reply-To: <20070121154012.GA26945@sbranzo.local> References: <20070121154012.GA26945@sbranzo.local> Message-ID: <0E4FA2F4-F2F3-494A-852B-997143362D38@geeklair.net> On Jan 21, 2007, at 10:40 AM, Sbranzo wrote: > Why does port look for commands in /sw/bin? I used to have > /sw/{bin,sbin} in my path (and in root's path too), but now I removed > all the references. It finds an appropriate tar when you install it. I would move aside fink (or at least remove it from your path) and reinstall macports from source. You can also set TAR and/or GNUTAR environment variables while building macports to get it to select the correct one. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20070121/b1bdc87e/PGP.bin From sbranzo at gmail.com Sun Jan 21 11:03:59 2007 From: sbranzo at gmail.com (Sbranzo) Date: Tue Oct 9 16:39:55 2007 Subject: Extraction command and fink conflict In-Reply-To: <0E4FA2F4-F2F3-494A-852B-997143362D38@geeklair.net> References: <20070121154012.GA26945@sbranzo.local> <0E4FA2F4-F2F3-494A-852B-997143362D38@geeklair.net> Message-ID: <20070121190358.GA322@sbranzo.local> On 21/01/07 12:02, Daniel J. Luke wrote: > It finds an appropriate tar when you install it. > > I would move aside fink (or at least remove it from your path) and > reinstall macports from source. It worked flawlessy. Thanks a lot. Gufo From john at jacelridge.com Sun Jan 21 17:57:27 2007 From: john at jacelridge.com (John Ridgway) Date: Tue Oct 9 16:39:55 2007 Subject: Naming of postgresql & related In-Reply-To: References: <3F37E552-5086-4B0B-8197-02AAF21F8300@macports.org> <1107CBE6-1374-4541-A1E6-CE4D1107E199@geeklair.net> Message-ID: On Jan 20, 2007, at 3:27 PM, Salvatore Domenick Desiano wrote: > We've had a couple of longish discussions about how to handle ports > with > multiple current versions. I think that mysql was the last such > debate. > Maybe we should have a "policy" about this. I'm thinking something > like > > - one port for each version that the project, itself, deems to be in > current service, each with the version number in it (in this case, > postgresql74 postgresql80 postgresql81 postgresql82) > > - one default, empty port which simply has a dependency on the most > recent version (in this case, postgresql, which depends on > postgresql82). > > This way, if people do it blindly (postgresql), they get the most > recent. If people write ports that need postgresql, they automatically > get a dependency on the most recent version. If a writer of another > port > (say, port "A") discovers that A only works with one specific version > of postgresql, they can use one of postgresql{74,81,82} as a > dependency. > In this case, it would be that port writer's responsibility to update > the Portfile for A to the most recent workable dependency (since > automatic upgrades have become a non-starter for A). > > Incidentally, I only think this should be used for specific ports > where > more than one major version is constantly in active use (apache, > mysql, > postgresql come to mind). In other cases a "beta" variant might be a > better approach. > Thoughts? > > -- Sal > smile. The problem with this is that I remember reading (somewhere) that variants should not change the version! Is that rule to be relaxed in the case of "beta" variants? Peace - John From ryandesign at macports.org Sun Jan 21 21:26:49 2007 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Oct 9 16:39:55 2007 Subject: intltool maintainer is macports-dev@lists.macosforge.org? Message-ID: <30DCAAD3-FE85-4EBF-9DEF-26942D17EA98@macports.org> What does it mean when a port's maintainer is macports- dev@lists.macosforge.org? The intltool port for example. Should that be changed to nomaintainer@macosports.org? From iane at sussex.ac.uk Mon Jan 22 02:12:10 2007 From: iane at sussex.ac.uk (Ian Eiloart) Date: Tue Oct 9 16:39:55 2007 Subject: Ticket 11232 was (Re: gmtl port file) In-Reply-To: References: <3FD533AE-4967-4C58-8371-62DAACCC1508@iastate.edu> <5FD946AA-4A94-4997-805C-DF1F705022A7@iastate.edu> Message-ID: --On 19 January 2007 12:47:43 -0800 "Jordan K. Hubbard" wrote: > > On Jan 18, 2007, at 11:05 PM, C?dric Luthi wrote: > >> Other than that, the port seems OK, but I don't have commit rights. > > Would you like some? We can always use people who are motivated enough > to go through TRAC and commit stuff! :-) > > - Jordan I'd like some. In fact, I think I was given some. However, I've never been able to log in to TRAC. Can someone fix that for me, please? My previous posts include some history on this. I think that I need a new account. -- Ian Eiloart IT Services, University of Sussex From rhwood at mac.com Mon Jan 22 02:32:07 2007 From: rhwood at mac.com (Randall Wood) Date: Tue Oct 9 16:39:55 2007 Subject: intltool maintainer is macports-dev@lists.macosforge.org? In-Reply-To: <30DCAAD3-FE85-4EBF-9DEF-26942D17EA98@macports.org> References: <30DCAAD3-FE85-4EBF-9DEF-26942D17EA98@macports.org> Message-ID: <707DADC8-72E5-481D-BC4E-485CD90CD831@mac.com> On 22 Jan 2007, at 00:26, Ryan Schmidt wrote: > What does it mean when a port's maintainer is macports- > dev@lists.macosforge.org? The intltool port for example. Should > that be changed to nomaintainer@macosports.org? Yes. That should be changed. A whole slew of ports got maintainers changes from darwinports@opendarwin.org to macports- dev@lists.macosforge.org before the nomaintainer/openmaintainer decision was made. > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-dev Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From rhwood at mac.com Mon Jan 22 02:48:04 2007 From: rhwood at mac.com (Randall Wood) Date: Tue Oct 9 16:39:55 2007 Subject: Naming of postgresql & related In-Reply-To: References: <3F37E552-5086-4B0B-8197-02AAF21F8300@macports.org> <1107CBE6-1374-4541-A1E6-CE4D1107E199@geeklair.net> Message-ID: On 21 Jan 2007, at 20:57, John Ridgway wrote: > > On Jan 20, 2007, at 3:27 PM, Salvatore Domenick Desiano wrote: >> >> Incidentally, I only think this should be used for specific ports >> where >> more than one major version is constantly in active use (apache, >> mysql, >> postgresql come to mind). In other cases a "beta" variant might be a >> better approach. > > The problem with this is that I remember reading (somewhere) that > variants should not change the version! Is that rule to be relaxed > in the case of "beta" variants? > It is a bad idea for variants to change versions if only because a new version of a port may require different patches, configure arguments, download different source code, etc, and lead to a massive, unwieldily, and most-likely difficult to read portfile. In addition, the port index will not be able to accurately reflect the port version or dependencies if that happens. Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From rhwood at mac.com Mon Jan 22 03:09:11 2007 From: rhwood at mac.com (Randall Wood) Date: Tue Oct 9 16:39:55 2007 Subject: bzip2 upgrade from 1.0.3 -> 1.0.4 Message-ID: <73ACD96E-FF08-42F8-A47B-68EF8643EFA5@mac.com> rhwood$ sudo port upgrade outdated ---> Deactivating bzip2 1.0.3_0 ---> Fetching bzip2 ---> Attempting to fetch bzip2-1.0.4.tar.gz from http://www.bzip.org/ 1.0.4/ ---> Verifying checksum(s) for bzip2 ---> Extracting bzip2 ---> Applying patches to bzip2 Error: Target com.apple.patch returned: shell command "cd "/opt/local/ var/db/dports/build/ _opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dp orts_archivers_bzip2/work/bzip2-1.0.4" && patch -p0 < "/opt/local/var/ db/dports/sources/rsync.rsync.darwinports.org_dpupdate_dports/ archivers/bzip2/files/patch-Makefile-dylib.diff"" returned error 1 Command output: patching file Makefile Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 4 out of 4 hunks ignored -- saving rejects to file Makefile.rej Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." From sbranzo at gmail.com Mon Jan 22 08:33:14 2007 From: sbranzo at gmail.com (Sbranzo) Date: Tue Oct 9 16:39:55 2007 Subject: bzip2 upgrade from 1.0.3 -> 1.0.4 In-Reply-To: <73ACD96E-FF08-42F8-