Marcus Calhoun-Lopez wrote:
> Sometime in the future (after discussion is complete), I was hoping to commit
> a
> change to the perl5 portgroup based on the discussion in #16830.
> (http://trac.macports.org/ticket/16830)
>
> I was also hoping to commit a python26 portgroup I have based on the
> d
Sometime in the future (after discussion is complete), I was hoping to commit a
change to the perl5 portgroup based on the discussion in #16830.
(http://trac.macports.org/ticket/16830)
I was also hoping to commit a python26 portgroup I have based on the
discussion in #16334.
(http://trac.macports.
On Oct 12, 2008, at 04:02, Anders F Björklund wrote:
> The configure scripts used the /Applications and /Library locations
> (or ~/Applications and ~/Library) because that was the rule at the
> time,
> made it easier to integrate with things outside of MacPorts itself
> such
> as Xcode or Serv
On Oct 11, 2008, at 11:40, [EMAIL PROTECTED] wrote:
> Revision: 40703
> http://trac.macports.org/changeset/40703
> Author: [EMAIL PROTECTED]
> Date: 2008-10-11 09:40:30 -0700 (Sat, 11 Oct 2008)
> Log Message:
> ---
> Version bump to 3.1.
>
> Modified Paths:
> --
On Sun, Oct 12, 2008 at 4:55 AM, Rainer Müller <[EMAIL PROTECTED]> wrote:
> Adam Byrtek wrote:
>> On Wed, Oct 1, 2008 at 5:13 AM, Rainer Müller <[EMAIL PROTECTED]> wrote:
>>> +1 on applying the patch.
>>
>> Thanks! Anybody with commit access willing to commit this?
>
> Committed in r40712.
Thank y
Bryan Blackburn wrote:
> We currently have an inconsistency concerning framework install
> locations:
> trunk, by default, sets frameworks_dir to /Library/Frameworks [1]; the
> python ports (2.4 and later versions) all use ${prefix}/Library/
> Frameworks.
I don't think the python ports follow
