unified python portgroup and different versions for different python versions

Hi There are a couple of ports I'd like to transition over to the python-1.0 portgroup but the complication is that different versions are required for different python versions. For example, one port requires version 1.x for python2 and version 2.x for python3. Is there a way to achieve this usin

Re: [MacPorts] ram modified

On Sun, Aug 14, 2011 at 00:58, Ryan Schmidt wrote: > FYI you can also use "sort -u"! Thanks, that's one less command to run. Cheers Adam ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/

Re: [82439] trunk/dports/python/py-dateutil/Portfile

On Sun, Aug 14, 2011 at 00:48, Ryan Schmidt wrote: > Why did you remove the modeline? We like modelines. Purely an oversight, it's back. Cheers Adam ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/l

Re: [82440] trunk/dports/python

On Sun, Aug 14, 2011 at 00:47, Ryan Schmidt wrote: > Since this changes where the documentation gets installed, you should > increase the port's revision. Good point, revision bumped. Cheers Adam ___ macports-dev mailing list macports-dev@lists.maco

Re: [MacPorts] ram modified

On Aug 13, 2011, at 12:38, MacPorts wrote: > > Changed page "ram" by r...@macports.org from 77.79.9.32* > Page URL: > Diff URL: > Revision 72 > -port list 'maintainer:(\W|^)ram(\W|$)' | awk '{ prin

Re: [82439] trunk/dports/python/py-dateutil/Portfile

On Aug 13, 2011, at 17:39, r...@macports.org wrote: > Revision: 82439 > http://trac.macports.org/changeset/82439 > Author: r...@macports.org > Date: 2011-08-13 15:39:20 -0700 (Sat, 13 Aug 2011) > Log Message: > --- > python/py-dateutil: update to 1.5 > > Modified Paths: >

Re: [82440] trunk/dports/python

On Aug 13, 2011, at 17:40, r...@macports.org wrote: > Revision: 82440 > http://trac.macports.org/changeset/82440 > Author: r...@macports.org > Date: 2011-08-13 15:40:22 -0700 (Sat, 13 Aug 2011) > Log Message: > --- > python/py*-dateutil: unify > post-destroot { > - set do

Re: Fwd: [82436] py-dnspython Lint Report

On Sat, Aug 13, 2011 at 17:19, Joshua Root wrote: > You get this whenever you add a new port and also add a dependency on it > in the same commit. The server just doesn't have the new port in its > index yet. Thanks Josh. That makes sense, I'll just ignore these then. Cheers Adam __

Re: Fwd: [82436] py-dnspython Lint Report

You get this whenever you add a new port and also add a dependency on it in the same commit. The server just doesn't have the new port in its index yet. - Josh On 2011-8-14 08:13 , Adam Mercer wrote: > Hi > > In updating a few of my ports to use the python-1.0 portgroup I've > been receiving ema

Fwd: [82436] py-dnspython Lint Report

Hi In updating a few of my ports to use the python-1.0 portgroup I've been receiving emails such as the one below regarding an unknown dependency. Is this anything to worry about? Cheets Adam -- Forwarded message -- From: Date: Sat, Aug 13, 2011 at 17:10 Subject: [82436] py-dn

Re: Unifying Python Ports

On 2011-8-14 06:09 , Blair Zajac wrote: > > On Aug 11, 2011, at 11:35 AM, Joshua Root wrote: > >> On 2011-8-12 03:51 , Jeremy Lavergne wrote: >>> As we unify python packages, will things depending on python2.4 packages >>> need the dependency name changed? >>> * py-some_py -> py24-some_py >>> *

Re: Unifying Python Ports

> port list maintainer:blair (something that finds all dependents matching py-*) port -q rdeps `port echo maintainer:blair and "py*"` | tr -d ' ' | sort -u smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-d

Re: Unifying Python Ports

On Aug 11, 2011, at 11:35 AM, Joshua Root wrote: > On 2011-8-12 03:51 , Jeremy Lavergne wrote: >> As we unify python packages, will things depending on python2.4 packages >> need the dependency name changed? >> * py-some_py -> py24-some_py >> * py-some_py -> py${python.version}-some_py >> >> Ot

$prefix/etc/profile.d

I'm proposing that MacPorts support the $prefix/etc/profile.d as a standard place where ports can install scripts that set up the user's environment. We would tell users to source everything in that directory from their ~/.profile or ~/.bash_profile. This would help us: - Multiple ports would

Re: [82163] trunk/dports/lang/llvm-devel/Portfile

Le 12 août 2011 à 06:17, Ryan Schmidt a écrit : > example if this is revision 123 from 2011-06-06 and this represents the > development effort leading up to llvm version 3.0, then the version line > might be "3.0-r123" or "3.0-20110606". Done in r82403. Have a nice week-end! Vincent __