Re: [MacPorts] TclVersionInfo modified
On Oct 23, 2013, at 14:59, MacPorts nore...@macports.org wrote: Page TclVersionInfo was changed by c...@macports.org Diff URL: https://trac.macports.org/wiki/TclVersionInfo?action=diffversion=7 Revision 7 Comment: Add Tcl VersionInfo for Mavericks Changes: ---8--8--8--8--8--8--8--8 Index: TclVersionInfo = --- TclVersionInfo (version: 6) +++ TclVersionInfo (version: 7) @@ -14,6 +14,7 @@ == Versions == ||= Mac OS X/Tcl =||= `/usr/bin/tclsh` =||= `/usr/bin/tclsh8.4` =||= `/usr/bin/tclsh8.5` =|| +||= 10.9 =||`8.5.9 ` ||`8.4.19 ` ||`8.5.9 ` || That explains why MacPorts is working at all on Mavericks. I expected they would have updated Tcl to 8.6 which would have broken MacPorts because of our nonstandard try/catch. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] Migration modified
On Oct 23, 2013, at 04:37, MacPorts nore...@macports.org wrote: Page Migration was changed by rai...@macports.org Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=58 Revision 58 Comment: Be more verbose on what to do for each OS X release Changes: ---8--8--8--8--8--8--8--8 Index: Migration = --- Migration (version: 57) +++ Migration (version: 58) @@ -3,11 +3,28 @@ An installation of MacPorts and the ports installed by it are only designed to work on a single OS release and a single CPU architecture. If you upgrade to a new OS version (e.g. from Leopard to Snow Leopard) or migrate to a new machine with a different type of CPU (e.g. PowerPC to Intel), you may get lucky and have your ports keep working, but in general, things will break. If you are only upgrading Xcode (e.g. 4.1 to 4.2 on Lion) but not the major OS version or CPU architecture, you do not need to reinstall ports as described below. -=== Reinstall Xcode and MacPorts === +=== Reinstall Xcode === -After performing either of these types of system upgrades, you will first need to [https://www.macports.org/install.php install the base MacPorts system] again, either from the appropriate disk image or from source. If you are upgrading from a prior version of Mac OS X, install the latest version of Xcode for your new OS. This will not be done for you automatically; Xcode is not updated by Software Update, so you must update it manually. For Lion, Xcode is available for free on the Mac App Store (after install you may also need to install Command Line Tools: XCode-Preferences-Downloads; if upgrading from previous version of xcode you may also need to do 'sudo xcode-select -switch /Applications/Xcode.app', [http://stackoverflow.com/questions/9849034/how-to-run-install-xcodebuild see this SO article]). For earlier OS versions, you will find the Xcode installer on the Mac OS X installation DVD or on the Apple Developer web site. +After performing either of these types of system upgrades, you will need to update the development tools. If you are upgrading from a prior version of Mac OS X, install the latest version of Xcode for your new OS. This will not be done for you automatically; Xcode is not updated by Software Update, so you must update it manually. -=== Update macports.conf === + Mac OS X 10.6 Snow Leopard and earlier + +You will find the Xcode installer on the Mac OS X installation DVD or on the Apple Developer web site. + + Mac OS X 10.7 Lion and OS X 10.8 Mountain Lion + +Xcode is available for free on the Mac App Store (after install you may also need to install Command Line Tools: XCode-Preferences-Downloads; if upgrading from previous version of xcode you may also need to do 'sudo xcode-select -switch /Applications/Xcode.app', [http://stackoverflow.com/questions/9849034/how-to-run-install-xcodebuild see this SO article]). + + Mac OS X 10.9 Mavericks + +For minimum support of MacPorts, you need the Command Line Tools, which can be installed using `xcode-select --install`. Note that some ports will require a full Xcode installation, which is available for free on the Mac App Store. + This is not the right place to explain how to install Xcode. We have a section in the Guide on how to do that; this page should just refer users there. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
clang-3.2 and earlier on Mavericks
Why are clang-3.2 and earlier not supported on Mavericks? This is inconvenient. It was very convenient to be able to install all versions of clang from 2.9 thru current on Mountain Lion, so that when bugs were reported on older Xcode versions I could simulate their environment without needing to change mine by changing configure.compiler to an earlier clang. Now to test for this I have to leave my primary machine and boot up another machine or VM with an earlier OS X version. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] TclVersionInfo modified
The link posted on macports-users http://www.opensource.apple.com/ is nice, since it leads also to all the tcl-versions shipped with Mac OS X since 10.0 (it was Tcl 8.3.2). -g Am 24.10.13 08:22, schrieb Ryan Schmidt: That explains why MacPorts is working at all on Mavericks. I expected they would have updated Tcl to 8.6 which would have broken MacPorts because of our nonstandard try/catch. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: clang-3.2 and earlier on Mavericks
On Oct 23, 2013, at 23:46, Ryan Schmidt ryandes...@macports.org wrote: Why are clang-3.2 and earlier not supported on Mavericks? This is inconvenient. It was very convenient to be able to install all versions of clang from 2.9 thru current on Mountain Lion, so that when bugs were reported on older Xcode versions I could simulate their environment without needing to change mine by changing configure.compiler to an earlier clang. Now to test for this I have to leave my primary machine and boot up another machine or VM with an earlier OS X version. They don't handle the 10.9 deployment target correctly. I think 3.3 may not as well and will require some patching. Using OSS versions of clang doesn't really simulate older Xcode clang versions. --Jeremy smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: clang-3.2 and earlier on Mavericks
On Oct 24, 2013, at 0:19, Ryan Schmidt ryandes...@macports.org wrote: On Oct 24, 2013, at 02:09, Jeremy Huddleston Sequoia wrote: Using OSS versions of clang doesn't really simulate older Xcode clang versions. I realize they are not identical but I have successfully used this technique multiple times to reproduce issues users experienced with older versions of Xcode clang and to develop fixes. Also I would like for llvm-3.2 to exist on Mavericks because my port pure requires it; pure does not work properly on OS X when using llvm-3.3 and after discussion with the developer we decided to leave MacPorts pure at llvm-3.2. https://groups.google.com/forum/#!searchin/pure-lang/pure-gen/pure-lang/JelRk7YHEug/upS-XGboNT8J In the last message of the thread, the developer of pure declared this to be “a genuine incompatibility between the x86 assembler backend in LLVM 3.3 and at least some Xcode versions, and no fix is known right now.” And without any radar of bug report at llvm.org (at least not any referenced in that thread), it's quite unlikely that any progress would ever be made on fixing such a bug... Could you followup with that thread to see if the pure developer ever got around to reporting this genuine incompatibility between the x86 assembler backend in LLVM 3.3 and at least some Xcode versions And I'll see about backporting the 10.9 deployment target patches to 3.2 when I get some cycles next week. I think the main issue is just the switch to libc++ default. --Jeremy smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
tesseract port
An update to the Tesseract port has been submitted, ticket #38871https://trac.macports.org/ticket/38871. Could someone take a look at it and commit the changes? dan ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
2.2.1
Are there any more changes that really need to go into 2.2.1, in particular any that are needed for Mavericks? Also, do we have any volunteers with Developer IDs to build pkgs for 10.8 and 10.9? (I apparently won't have supported hardware until December.) - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Should you upgrade to Mavericks?
Moved to DEV On Oct 23, 2013, at 9:24 PM, Ryan Schmidt ryandes...@macports.org wrote: At this time, MacPorts does not offer a pre-compiled release for Mavericks. You can build MacPorts trunk from source and it appears to work on Mavericks. We will try to make a new release soon. so, you've been telling a bunch of people to use trunk - what's fixed in trunk that's broken in the latest release? I rebuilt the latest release (selfupdate -f) and ran port upgrade outdated and have 694 ports that look like they rebuild successfully :) [yes, I know that I didn't follow the migration instructions, but I'm prepared to fix anything that is broken] -- Daniel J. Luke ++ | * dl...@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 https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Should you upgrade to Mavericks?
On Thu, Oct 24, 2013 at 10:05:50AM -0400, Daniel J. Luke wrote: so, you've been telling a bunch of people to use trunk - what's fixed in trunk that's broken in the latest release? http://trac.macports.org/changeset/110985 That's pretty much the only change related to Mavericks on the release branch for 2.2.1 at the moment. A couple of other changes for 2.2.1 are documented in http://trac.macports.org/changeset/112486/branches/release_2_2/base but those aren't strictly required for Mavericks. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Should you upgrade to Mavericks?
On 2013-10-25 01:05 , Daniel J. Luke wrote: Moved to DEV On Oct 23, 2013, at 9:24 PM, Ryan Schmidt ryandes...@macports.org wrote: At this time, MacPorts does not offer a pre-compiled release for Mavericks. You can build MacPorts trunk from source and it appears to work on Mavericks. We will try to make a new release soon. so, you've been telling a bunch of people to use trunk - what's fixed in trunk that's broken in the latest release? I rebuilt the latest release (selfupdate -f) and ran port upgrade outdated and have 694 ports that look like they rebuild successfully :) [yes, I know that I didn't follow the migration instructions, but I'm prepared to fix anything that is broken] Yeah, I'd really rather not encourage users to install trunk, since all too often that means they keep running some random trunk revision and miss out on new base versions because selfupdate sees e.g. 2.2.99 2.2.1. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: 2.2 on Mavericks
Joshua Root j...@macports.org wrote: Please use MacPorts trunk for Mavericks; MacPorts 2.2.0 is not supported on Mavericks. People keep saying that, but what are the actual problems with 2.2? I have just installed a fresh MacPorts 2.2.0 on Mavericks. So far, no problem. Except that atlas didn't compile (gnutar not found in the log). So I installed the gnutar port, and now atlas seems to be compiling fine so far. -- http://www.juliensalort.org ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: 2.2 on Mavericks
On 2013-10-25 01:44 , Julien Salort wrote: Joshua Root j...@macports.org wrote: Please use MacPorts trunk for Mavericks; MacPorts 2.2.0 is not supported on Mavericks. People keep saying that, but what are the actual problems with 2.2? I have just installed a fresh MacPorts 2.2.0 on Mavericks. So far, no problem. Except that atlas didn't compile (gnutar not found in the log). So I installed the gnutar port, and now atlas seems to be compiling fine so far. Right, that's a problem with the atlas port. It defines a custom extract phase and runs gnutar specifically. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Delete stray file from git-extras on buildbots
Hi Bill, there is a stray file on the build bots for Lion and Snow Leopard as git-extras wrote to the prefix directly instead of to the destroot. Can you please delete '/opt/local/etc/bash_completion.d/git-extras'? Failing builds: https://build.macports.org/builders/buildports-lion-x86_64/builds/15320 https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/21668 Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: tesseract port
On Oct 24, 2013, at 08:00, M. Daniel Becque mdbec...@gmail.com wrote: An update to the Tesseract port has been submitted, ticket #38871. Could someone take a look at it and commit the changes? Done! ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Delete stray file from git-extras on buildbots
On Oct 24, 2013, at 10:16, Rainer Müller wrote: there is a stray file on the build bots for Lion and Snow Leopard as git-extras wrote to the prefix directly instead of to the destroot. Can you please delete '/opt/local/etc/bash_completion.d/git-extras'? This problem will affect user systems as well, won’t it? Instead of making the Mac OS Forge admin and all users who have installed this port delete this manually, you should make the port delete it automatically. See the post-activate block of the lisaem port for an example of how this can be done (except that if this is a file that the port will now install, it should be pre-activate instead). ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Delete stray file from git-extras on buildbots
On Oct 24, 2013, at 11:16 AM, Rainer Müller rai...@macports.org wrote: there is a stray file on the build bots for Lion and Snow Leopard as git-extras wrote to the prefix directly instead of to the destroot. Can you please delete '/opt/local/etc/bash_completion.d/git-extras'? Failing builds: https://build.macports.org/builders/buildports-lion-x86_64/builds/15320 https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/21668 when I had a port that did something similar, ryan reminded me that it's also a problem on any user's machine who installed the port - so you need to take care of it in the port. I copied a recipe from somewhere else and added it to subversion-javahlbindings a while back. -- Daniel J. Luke ++ | * dl...@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 https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [112484] trunk/dports/devel/libsdl2/Portfile
On Oct 24, 2013, at 08:08, j...@macports.org wrote: Revision 112484 Author j...@macports.org Date 2013-10-24 06:08:55 -0700 (Thu, 24 Oct 2013) Log Message libsdl2: update to 2.0.1 libsdl2 replaces libsdl-devel, doesn’t it? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Delete stray file from git-extras on buildbots
On 2013-10-24 17:33, Ryan Schmidt wrote: On Oct 24, 2013, at 10:16, Rainer Müller wrote: there is a stray file on the build bots for Lion and Snow Leopard as git-extras wrote to the prefix directly instead of to the destroot. Can you please delete '/opt/local/etc/bash_completion.d/git-extras'? This problem will affect user systems as well, won’t it? Instead of making the Mac OS Forge admin and all users who have installed this port delete this manually, you should make the port delete it automatically. See the post-activate block of the lisaem port for an example of how this can be done (except that if this is a file that the port will now install, it should be pre-activate instead). Thank you and Daniel for the hint. As the access was blocked due to sandboxing on my system, I did not consider that anyone else would have the file... I fixed it and the buildbots now finished the build of git-extras. https://trac.macports.org/changeset/112498 Rainer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [112484] trunk/dports/devel/libsdl2/Portfile
On 2013-10-25 03:00 , Ryan Schmidt wrote: On Oct 24, 2013, at 08:08, j...@macports.org wrote: Revision 112484 Author j...@macports.org Date 2013-10-24 06:08:55 -0700 (Thu, 24 Oct 2013) Log Message libsdl2: update to 2.0.1 libsdl2 replaces libsdl-devel, doesn’t it? Sort of. The next major release of SDL was originally going to be 1.3, and be compatible with 1.2. The compatibility was eventually abandoned, and the release was called 2.0. I'm not sure where libsdl-devel fits along this timeline. Probably not much point keeping it around in any case. On another point related to this, someone apparently went through and changed most of the port:libsdl dependencies to path:lib/pkgconfig/sdl.pc:libsdl without checking if the ports worked with libsdl-devel as well as libsdl. It's likely many of them should be changed back. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [112484] trunk/dports/devel/libsdl2/Portfile
On Oct 24, 2013, at 11:57, Joshua Root wrote: On 2013-10-25 03:00 , Ryan Schmidt wrote: On Oct 24, 2013, at 08:08, j...@macports.org wrote: Revision 112484 Author j...@macports.org Date 2013-10-24 06:08:55 -0700 (Thu, 24 Oct 2013) Log Message libsdl2: update to 2.0.1 libsdl2 replaces libsdl-devel, doesn’t it? Sort of. The next major release of SDL was originally going to be 1.3, and be compatible with 1.2. The compatibility was eventually abandoned, and the release was called 2.0. I'm not sure where libsdl-devel fits along this timeline. Probably not much point keeping it around in any case. Right. I believe the version of libsdl-devel we have now is a) old and b) not compatible with libsdl. On another point related to this, someone apparently went through and changed most of the port:libsdl dependencies to path:lib/pkgconfig/sdl.pc:libsdl without checking if the ports worked with libsdl-devel as well as libsdl. It's likely many of them should be changed back. Right. They were changed because that’s the promise of the “*-devel” naming: that it’s compatible with the original “*” port. Since that compatibility doesn’t exist anymore and the port will be deleted, the dependencies can be changed back. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [112484] trunk/dports/devel/libsdl2/Portfile
On Oct 24, 2013, at 11:59, Ryan Schmidt ryandes...@macports.org wrote: Since that compatibility doesn’t exist anymore and the port will be deleted, the dependencies can be changed back. Or rather, we can figure out which ports now need libsdl2 and which still need libsdl. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: 2.2.1
On Oct 24, 2013, at 12:14, Adam Mercer wrote: On Thu, Oct 24, 2013 at 2:25 PM, Joshua Root j...@macports.org wrote: Also, do we have any volunteers with Developer IDs to build pkgs for 10.8 and 10.9? (I apparently won't have supported hardware until December.) I can do 10.9 right away but won't be able to do 10.8 until I get back to the office on 8 November. If someone else could build 10.8 I could sign that package with my certificate. I can build for any OS X version, but don’t have developer ID. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [112504] trunk/dports/devel
On Oct 24, 2013, at 12:56, t...@macports.org wrote: Revision 112504 Author t...@macports.org Date 2013-10-24 10:56:07 -0700 (Thu, 24 Oct 2013) Log Message remove obsolete libsdl-devel port We might want to leave a stub libsdl-devel port marked as “replaced_by libsdl” (or “replaced_by libsdl2”) for awhile. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: open tickets
Hi committers, I'd like to ask again for someone to take a look at these two tickets, for a maintainer patch and taking over an abandoned port. Thanks, David On Sun, Oct 6, 2013 at 11:15 PM, David Strubbe dstru...@gmail.com wrote: Hi committers, Can you please take a look at two open tickets I submitted? The first is an enhancement to my sparskit port; the second is about port abandonment of libxc. I submitted it 5 days ago, so the 72 hour timeout period has elapsed. Thanks, David [1] https://trac.macports.org/ticket/40638 [2] https://trac.macports.org/ticket/40646 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
port lint: version hardcoded in license
In case someone wants to get to it before I do, the hardcoded version check thinks the license field might contain a port's version. Just have it skip that field/line. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: open tickets
Handled. Have you applied for commit access? On Oct 24, 2013, at 5:20 PM, David Strubbe wrote: Hi committers, I'd like to ask again for someone to take a look at these two tickets, for a maintainer patch and taking over an abandoned port. Thanks, David On Sun, Oct 6, 2013 at 11:15 PM, David Strubbe dstru...@gmail.com wrote: Hi committers, Can you please take a look at two open tickets I submitted? The first is an enhancement to my sparskit port; the second is about port abandonment of libxc. I submitted it 5 days ago, so the 72 hour timeout period has elapsed. Thanks, David [1] https://trac.macports.org/ticket/40638 [2] https://trac.macports.org/ticket/40646 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: open tickets
Thanks! Yes, I sent an email to macports-...@lists.macosforge.org about a month ago regarding commit access, as specified by the guide, and a reminder a couple of weeks ago, but I didn't hear anything back. David On Thu, Oct 24, 2013 at 5:41 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Handled. Have you applied for commit access? On Oct 24, 2013, at 5:20 PM, David Strubbe wrote: Hi committers, I'd like to ask again for someone to take a look at these two tickets, for a maintainer patch and taking over an abandoned port. Thanks, David On Sun, Oct 6, 2013 at 11:15 PM, David Strubbe dstru...@gmail.com wrote: Hi committers, Can you please take a look at two open tickets I submitted? The first is an enhancement to my sparskit port; the second is about port abandonment of libxc. I submitted it 5 days ago, so the 72 hour timeout period has elapsed. Thanks, David [1] https://trac.macports.org/ticket/40638 [2] https://trac.macports.org/ticket/40646 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: open tickets
Yeah it can take a while to hear anything back... I sent in an application back in May and I haven't really heard anything back, either... On Thu, Oct 24, 2013 at 5:52 PM, David Strubbe dstru...@gmail.com wrote: Thanks! Yes, I sent an email to macports-...@lists.macosforge.org about a month ago regarding commit access, as specified by the guide, and a reminder a couple of weeks ago, but I didn't hear anything back. David On Thu, Oct 24, 2013 at 5:41 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Handled. Have you applied for commit access? On Oct 24, 2013, at 5:20 PM, David Strubbe wrote: Hi committers, I'd like to ask again for someone to take a look at these two tickets, for a maintainer patch and taking over an abandoned port. Thanks, David On Sun, Oct 6, 2013 at 11:15 PM, David Strubbe dstru...@gmail.com wrote: Hi committers, Can you please take a look at two open tickets I submitted? The first is an enhancement to my sparskit port; the second is about port abandonment of libxc. I submitted it 5 days ago, so the 72 hour timeout period has elapsed. Thanks, David [1] https://trac.macports.org/ticket/40638 [2] https://trac.macports.org/ticket/40646 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] MavericksProblems modified
No no no no no. Never edit Apple Land. On Oct 24, 2013, at 7:21 PM, MacPorts wrote: then install and symlink to /usr/bin/gnutar. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
