On 2012-5-24 10:14 , Ryan Schmidt wrote:
>
> It seems weird to me that a change in the portgroup should be allowed to
> create new subports in ports that have not themselves been modified to
> indicate that that's ok. It seems to me that instead each p5 port should be
> specifying which perl ve
On May 23, 2012, at 20:25, Bjarne D Mathiesen wrote:
> So ... portindex is -as a minimum- _unable_ to combine a private repo
> with the official repo in a case like this.
portindex always only concerns itself with the single ports tree you're running
the command in.
_
Ryan Schmidt wrote:
>
> On May 22, 2012, at 15:12, Bjarne D Mathiesen wrote:
>
>> Ryan Schmidt wrote:
>>>
>>> On May 22, 2012, at 14:27, Bjarne D Mathiesen wrote:
>>>
MacPorts wrote:
> #34570: perl5.16 - new port
> --+--
On May 23, 2012, at 8:14 p.m., Ryan Schmidt wrote:
> It seems weird to me that a change in the portgroup should be allowed to
> create new subports in ports that have not themselves been modified to
> indicate that that's ok. It seems to me that instead each p5 port should be
> specifying which
On May 22, 2012, at 15:12, Bjarne D Mathiesen wrote:
> Ryan Schmidt wrote:
>>
>> On May 22, 2012, at 14:27, Bjarne D Mathiesen wrote:
>>
>>> MacPorts wrote:
#34570: perl5.16 - new port
--+-
Reporter: macinto
Ryan Schmidt wrote:
>
> On May 22, 2012, at 14:27, Bjarne D Mathiesen wrote:
>
>> MacPorts wrote:
>>> #34570: perl5.16 - new port
>>> --+-
>>> Reporter: macintosh@… | Owner: macports-tickets@…
>>>
On May 22, 2012, at 14:27, Bjarne D Mathiesen wrote:
> MacPorts wrote:
>> #34570: perl5.16 - new port
>> --+-
>> Reporter: macintosh@… | Owner: macports-tickets@…
>>
>> Type: sub
MacPorts wrote:
> #34570: perl5.16 - new port
> --+-
> Reporter: macintosh@… | Owner: macports-tickets@…
>
> Type: submission| Status: new
