Yeah, this perl situation drives me crazy. I always wind up accidentally
installing 5.12 when I don't want to, and I still have yet to install 5.18,
although I am looking at how to build that. I'm with Daniel. We should just
keep the latest stable(5.18) and p5-* and keep the perl5-XXs around if you
On Jul 8, 2013, at 10:44 AM, Jeremy Huddleston Sequoia
wrote:
>> do you have a reason why? We generally follow the upstream 'stable' release
>> unless we've got a specific reason not to...
>
> Well that wasn’t the case while 5.14 was stable upstream nor while 5.16 was
> stable upstream.
and
On Jul 8, 2013, at 7:17 AM, Daniel J. Luke wrote:
> On Jul 5, 2013, at 2:57 AM, Jeremy Huddleston Sequoia
> wrote:
>> TBH, I’d rather switch to 5.16 while 5.18 matures in MacPorts ...
>
> do you have a reason why? We generally follow the upstream 'stable' release
> unless we've got a specifi
On Jul 5, 2013, at 2:57 AM, Jeremy Huddleston Sequoia
wrote:
> TBH, I’d rather switch to 5.16 while 5.18 matures in MacPorts ...
do you have a reason why? We generally follow the upstream 'stable' release
unless we've got a specific reason not to...
--
Daniel J. Luke
On 2013-7-5 16:57 , Jeremy Huddleston Sequoia wrote:
> TBH, I’d rather switch to 5.16 while 5.18 matures in MacPorts ...
>
> So is anyone against moving from 5.12 to 5.16 as the default? Should we make
> changes to all the relevant ports at once?
Yes, they should all be changed at once. For per
TBH, I’d rather switch to 5.16 while 5.18 matures in MacPorts ...
So is anyone against moving from 5.12 to 5.16 as the default? Should we make
changes to all the relevant ports at once?
On Jun 19, 2013, at 10:49 AM, Daniel J. Luke wrote:
> On Jun 19, 2013, at 1:25 PM, Frank Schima
> wrote:
On Jul 1, 2013, at 10:58 AM, Jeremy Huddleston Sequoia
wrote:
>> Still doesn't work. perl5.major isn't guaranteed to be the same at build
>> time and activation time. (And what do dependents use for INTLTOOL_PERL?)
>
> So then do we really need variants for each perl version in each dependent
On Jul 1, 2013, at 10:33 AM, Joshua Root wrote:
> On 2013-7-2 02:30 , Jeremy Huddleston Sequoia wrote:
>>
>> On Jul 1, 2013, at 3:44 AM, Joshua Root wrote:
>>
> Anything that depends on intltool and uses the standard autoconf macros
> to check for it also needs to be updated when intl
On 2013-7-2 02:30 , Jeremy Huddleston Sequoia wrote:
>
> On Jul 1, 2013, at 3:44 AM, Joshua Root wrote:
>
Anything that depends on intltool and uses the standard autoconf macros
to check for it also needs to be updated when intltool is,
unfortunately. INTLTOOL_PERL needs to match
On 2013-07-01 18:30, Jeremy Huddleston Sequoia wrote:
> So then is this the correct approach we should be taking:
>
> Index: Portfile
> ===
> --- Portfile (revision 107485)
> +++ Portfile (working copy)
> @@ -2,9 +2,11 @@
> # $Id$
On Jul 1, 2013, at 3:44 AM, Joshua Root wrote:
>>> Anything that depends on intltool and uses the standard autoconf macros
>>> to check for it also needs to be updated when intltool is,
>>> unfortunately. INTLTOOL_PERL needs to match the perl used by intltool,
>>> or the configure script complai
On 2013-7-1 17:34 , Jeremy Huddleston Sequoia wrote:
>
> On Jun 19, 2013, at 12:44 PM, Joshua Root wrote:
>
>> Anything that depends on intltool and uses the standard autoconf macros
>> to check for it also needs to be updated when intltool is,
>> unfortunately. INTLTOOL_PERL needs to match the
On Jun 19, 2013, at 12:44 PM, Joshua Root wrote:
> On 2013-6-20 02:02 , Frank Schima wrote:
>> It seems to me that we should be switching the default perl in Macports
>> from version 5.12 to 5.16. Are there any objections to this? If not, I
>> will create a Trac ticket about this.
>>
>> Here ar
On Jun 19, 2013, at 11:02, Frank Schima wrote:
> Here are the ports that need to be changed (46 total). Generated with the
> following command:
>
> port echo depends:perl5.12 and not 'p5.12-*'
I doubt that's anywhere near all of them. What about all the ports that declare
a dependency on a p5
On 2013-6-20 02:02 , Frank Schima wrote:
> It seems to me that we should be switching the default perl in Macports
> from version 5.12 to 5.16. Are there any objections to this? If not, I
> will create a Trac ticket about this.
>
> Here are the ports that need to be changed (46 total). Generated w
On Jun 19, 2013, at 1:25 PM, Frank Schima wrote:
> On Jun 19, 2013, at 10:06 AM, Daniel J. Luke wrote:
>> On Jun 19, 2013, at 12:02 PM, Frank Schima
>> wrote:
>>>
>>> It seems to me that we should be switching the default perl in Macports
>>> from version 5.12 to 5.16. Are there any objection
On Jun 19, 2013, at 11:25 AM, Frank Schima wrote:
>
> On Jun 19, 2013, at 10:06 AM, Daniel J. Luke wrote:
>
>> On Jun 19, 2013, at 12:02 PM, Frank Schima
>> wrote:
>>>
>>> It seems to me that we should be switching the default perl in Macports
>>> from version 5.12 to 5.16. Are there any
On Jun 19, 2013, at 10:06 AM, Daniel J. Luke wrote:
> On Jun 19, 2013, at 12:02 PM, Frank Schima
> wrote:
>>
>> It seems to me that we should be switching the default perl in Macports from
>> version 5.12 to 5.16. Are there any objections to this? If not, I will
>> create a Trac ticket abou
On Jun 19, 2013, at 12:02 PM, Frank Schima wrote:
>
> It seems to me that we should be switching the default perl in Macports from
> version 5.12 to 5.16. Are there any objections to this? If not, I will create
> a Trac ticket about this.
do you mean 5.18, or are we desiring to continue to be
It seems to me that we should be switching the default perl in Macports from
version 5.12 to 5.16. Are there any objections to this? If not, I will create a
Trac ticket about this.
Here are the ports that need to be changed (46 total). Generated with the
following command:
port echo depends:pe
20 matches
Mail list logo
