Re: build.args arg="FLAG1 FLAG2"

2011-07-04 Thread Joshua Root
On 2011-7-5 11:31 , Jeremy Lavergne wrote: >> This sounds very similar to what postfix does. > > postfix employs ldelete as well, but I'm curious must one re-set the variable > (CCARGS) after deleting from it? Yep. It works like lreplace, which returns a new list and doesn't modify the original

Re: build.args arg="FLAG1 FLAG2"

2011-07-04 Thread Jeremy Lavergne
Here's what I've come up with so far; let me know if you have further suggestions. * revbump * gutted no_ variants and made them require the negative of the new variants * new variants conflict with no_ variants, utilize lappend/ldelete * marked date with comment, at a suitable time in the fu

Re: build.args arg="FLAG1 FLAG2"

2011-07-04 Thread Jeremy Lavergne
> This sounds very similar to what postfix does. postfix employs ldelete as well, but I'm curious must one re-set the variable (CCARGS) after deleting from it? variant pcre description "add pcre support" { set CCARGS [ldelete ${CCARGS} -DNO_PCRE] lappend CCARGS -DHAS_PCRE "-I${pref

Re: build.args arg="FLAG1 FLAG2"

2011-07-04 Thread Jeremy Lavergne
> This sounds very similar to what postfix does. Perfect! Use lappend in variant blocks to manage a list and then for build phase have build.args set equal to the list---it converts! smime.p7s Description: S/MIME cryptographic signature ___ macports-

Re: build.args arg="FLAG1 FLAG2"

2011-07-04 Thread Joshua Root
On 2011-7-5 11:02 , Jeremy Lavergne wrote: > I've got a port that's using +no_ variants presently. I'd like to migrate it > off but I'm not sure I can replicate the build.args behavior necessary to > deal with the setup. You see, build.args takes one argument but it has > several values in it. >

build.args arg="FLAG1 FLAG2"

2011-07-04 Thread Jeremy Lavergne
I've got a port that's using +no_ variants presently. I'd like to migrate it off but I'm not sure I can replicate the build.args behavior necessary to deal with the setup. You see, build.args takes one argument but it has several values in it. build.args ARG="-DVALUE1 -DVALUE2 -DVALUE3" We've

Re: what's the plan for mac os x lion

2011-07-04 Thread Jack Howarth
On Mon, Jul 04, 2011 at 08:27:27PM -0400, Jack Howarth wrote: > On Mon, Jul 04, 2011 at 04:48:24PM -0700, Jeremy Huddleston wrote: > > > > On Jul 4, 2011, at 14:04, Jack Howarth wrote: > > > > > On Mon, Jul 04, 2011 at 01:29:31PM -0700, Blair Zajac wrote: > > >> > > >> On Jul 4, 2011, at 11:30 A

Re: what's the plan for mac os x lion

2011-07-04 Thread Jack Howarth
On Mon, Jul 04, 2011 at 04:48:24PM -0700, Jeremy Huddleston wrote: > > On Jul 4, 2011, at 14:04, Jack Howarth wrote: > > > On Mon, Jul 04, 2011 at 01:29:31PM -0700, Blair Zajac wrote: > >> > >> On Jul 4, 2011, at 11:30 AM, Jack Howarth wrote: > >> > >>> On Mon, Jul 04, 2011 at 11:16:48AM -0700,

Re: archivefetch and trunk

2011-07-04 Thread Jeremy Lavergne
> Looks like you used -b and there was no archive available. Got it. The env variable ARCHIVE_SITE_LOCAL wasn't set. Thanks for the tip off ;-) smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.m

Re: archivefetch and trunk

2011-07-04 Thread Jeremy Lavergne
> Looks like you used -b and there was no archive available. Isn't that why it's trying to fetch the archive then? smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macos

Re: archivefetch and trunk

2011-07-04 Thread Joshua Root
On 2011-7-5 01:19 , Jeremy Lavergne wrote: > I seem to have run into an issue with archivefetch failing. It doesn't seem > to be directly related to that though, more like a missing file: > DEBUG: couldn't open > "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": > no su

Re: what's the plan for mac os x lion

2011-07-04 Thread Jeremy Huddleston
On Jul 4, 2011, at 14:04, Jack Howarth wrote: > On Mon, Jul 04, 2011 at 01:29:31PM -0700, Blair Zajac wrote: >> >> On Jul 4, 2011, at 11:30 AM, Jack Howarth wrote: >> >>> On Mon, Jul 04, 2011 at 11:16:48AM -0700, Blair Zajac wrote: On Jul 4, 2011, at 11:14 AM, Jeremy Huddleston wrote:

Re: what's the plan for mac os x lion

2011-07-04 Thread Jack Howarth
On Mon, Jul 04, 2011 at 01:29:31PM -0700, Blair Zajac wrote: > > On Jul 4, 2011, at 11:30 AM, Jack Howarth wrote: > > > On Mon, Jul 04, 2011 at 11:16:48AM -0700, Blair Zajac wrote: > >> On Jul 4, 2011, at 11:14 AM, Jeremy Huddleston wrote: > >>> > >>> All of the ports that are in my install-set

Re: what's the plan for mac os x lion

2011-07-04 Thread Ryan Schmidt
On Jul 4, 2011, at 13:16, Blair Zajac wrote: > Out of curiosity, Apple hasn't bumped to a newer gcc version? Does anybody > know why? My understanding is that newer GCC versions are released under version 3 of the GPL, and that Apple does not like that version of the license. http://apple.s

Re: what's the plan for mac os x lion

2011-07-04 Thread Blair Zajac
On Jul 4, 2011, at 11:30 AM, Jack Howarth wrote: > On Mon, Jul 04, 2011 at 11:16:48AM -0700, Blair Zajac wrote: >> On Jul 4, 2011, at 11:14 AM, Jeremy Huddleston wrote: >>> >>> All of the ports that are in my install-set (including many multimedia >>> ports, x11, firefox, gnome, with most bloat

Re: what's the plan for mac os x lion

2011-07-04 Thread Jeremy Huddleston
On Jul 4, 2011, at 11:16, Blair Zajac wrote: > On Jul 4, 2011, at 11:14 AM, Jeremy Huddleston wrote: >> >> All of the ports that are in my install-set (including many multimedia >> ports, x11, firefox, gnome, with most bloat variants set) have been working >> with trunk/base using llvm-gcc-4.2

Re: what's the plan for mac os x lion

2011-07-04 Thread Jack Howarth
On Mon, Jul 04, 2011 at 11:16:48AM -0700, Blair Zajac wrote: > On Jul 4, 2011, at 11:14 AM, Jeremy Huddleston wrote: >> >> All of the ports that are in my install-set (including many multimedia >> ports, x11, firefox, gnome, with most bloat variants set) have been >> working with trunk/base using

Re: what's the plan for mac os x lion

2011-07-04 Thread Blair Zajac
On Jul 4, 2011, at 11:14 AM, Jeremy Huddleston wrote: All of the ports that are in my install-set (including many multimedia ports, x11, firefox, gnome, with most bloat variants set) have been working with trunk/base using llvm-gcc-4.2 on SL and Lion for a while now (trunk/base now chooses

Re: what's the plan for mac os x lion

2011-07-04 Thread Jeremy Huddleston
On Jul 4, 2011, at 09:00, Jordan K. Hubbard wrote: > > On Jul 4, 2011, at 5:27 AM, S. M. Ibrahim (Lavlu) wrote: > >> mac os x lion is already in GM state. Are macports ready for it ? i >> installed macports from source (trunk) , but lot's of package failed to >> build. but not reporting it on

Re: what's the plan for mac os x lion

2011-07-04 Thread Jordan K. Hubbard
On Jul 4, 2011, at 5:27 AM, S. M. Ibrahim (Lavlu) wrote: > mac os x lion is already in GM state. Are macports ready for it ? i installed > macports from source (trunk) , but lot's of package failed to build. but not > reporting it on trac as i saw one ticket was closed with "we are not giving

Re: what's the plan for mac os x lion

2011-07-04 Thread Jordan K. Hubbard
On Jul 4, 2011, at 5:27 AM, S. M. Ibrahim (Lavlu) wrote: > mac os x lion is already in GM state. Are macports ready for it ? i installed > macports from source (trunk) , but lot's of package failed to build. but not > reporting it on trac as i saw one ticket was closed with "we are not giving

Re: archivefetch and trunk

2011-07-04 Thread Jeremy Lavergne
Btw, this is what is in my Tcl resources folder: $ ls -F /System/Library/Frameworks/Tcl.framework/Versions/8.5/ResourcesDocumentation/ Info.plist Scripts/ license.terms tcl8/ version.plist On Jul 4, 2011, at 11:19 , Jeremy Lavergne wrote: > DEBUG: couldn't open > "/System/Library/Frameworks/Tcl

archivefetch and trunk

2011-07-04 Thread Jeremy Lavergne
I seem to have run into an issue with archivefetch failing. It doesn't seem to be directly related to that though, more like a missing file: DEBUG: couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory I've done `make distclean` and

Re: Changes for pari 2.5.0

2011-07-04 Thread Vincent Lefevre
Hi Jeremy, On 2011-07-03 17:31:46 -0700, Jeremy Huddleston wrote: > Hey vincent, > > I noticed that the banner printed in pari incorrectly identifies the compiler > when building with clang. > > I is being reported as "gcc-3.0": > >

Re: Changes for pari 2.5.0

2011-07-04 Thread Vincent Lefevre
On 2011-07-02 05:16:27 -0500, Ryan Schmidt wrote: > There may be legitimate cases for overriding the default variant description, > to provide more info (like pari and perhaps glew). Not sure what we should > do. Either leave things the way they are (and let the port author get a lint > warning

what's the plan for mac os x lion

2011-07-04 Thread S. M. Ibrahim (Lavlu)
hi, mac os x lion is already in GM state. Are macports ready for it ? i installed macports from source (trunk) , but lot's of package failed to build. but not reporting it on trac as i saw one ticket was closed with "we are not giving support for lion" (something like this). now my question, is m

RE: kile-devel to stable version

2011-07-04 Thread Russell Jones
I don't know if there's a policy, but kile-kde4 would seem like a more descriptive name. I can't really find any port names of that form, though. Alternatively kile21, (like python25. emacs22, etc) Russell From: macports-dev-boun...@lists.macosforge.org