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-

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 wrote: > Thanks! > > Yes, I sent an email to macports-...@lists.macosforge.org about a month > ago regarding

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 wrote: > Handled. > > Have you

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, 201

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.macosf

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 wrote: > Hi committers, > > Can you please take a look at two open tickets I submitted?

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 “rep

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 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

Re: [112484] trunk/dports/devel/libsdl2/Portfile

On Oct 24, 2013, at 11:59, Ryan Schmidt 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. ___

Re: 2.2.1

On Thu, Oct 24, 2013 at 2:25 PM, Joshua Root 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 Novem

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 >>> >>> libsd

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’

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/

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? ___ macp

Re: Delete stray file from git-extras on buildbots

On Oct 24, 2013, at 11:16 AM, 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'? > > Failing builds: > https://buil

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 system

Re: tesseract port

On Oct 24, 2013, at 08:00, M. Daniel Becque 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 h

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/

Re: 2.2 on Mavericks

On 2013-10-25 01:44 , Julien Salort wrote: > Joshua Root 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 Maveric

Re: 2.2 on Mavericks

Joshua Root 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 com

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 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

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

Re: Should you upgrade to Mavericks?

Moved to DEV On Oct 23, 2013, at 9:24 PM, Ryan Schmidt 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

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 __

tesseract port

An update to the Tesseract port has been submitted, 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.macosforg

Re: clang-3.2 and earlier on Mavericks

On Oct 24, 2013, at 0:19, Ryan Schmidt 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 t

Re: clang-3.2 and earlier on Mavericks

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

Re: clang-3.2 and earlier on Mavericks

On Oct 23, 2013, at 23:46, Ryan Schmidt 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 vers

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