On Nov 15, 2011, at 01:09, Joshua Root wrote:
> On 2011-11-15 09:10 , Ryan Schmidt wrote:
>>
>> On Nov 13, 2011, at 23:56, Joshua Root wrote:
>>
>>> On 2011-11-14 16:38 , Ryan Schmidt wrote:
I wasn't sure what would happen when you change the case of the port name
like that. Wil
On 2011-11-15 09:10 , Ryan Schmidt wrote:
>
> On Nov 13, 2011, at 23:56, Joshua Root wrote:
>
>> On 2011-11-14 16:38 , Ryan Schmidt wrote:
>>>
>>> I wasn't sure what would happen when you change the case of the port name
>>> like that. Will users who had qlipper @1.8.2_0 installed get prompted t
On Nov 13, 2011, at 23:56, Joshua Root wrote:
> On 2011-11-14 16:38 , Ryan Schmidt wrote:
>>
>> I wasn't sure what would happen when you change the case of the port name
>> like that. Will users who had qlipper @1.8.2_0 installed get prompted to
>> upgrade to Qlipper @1.8.2_1? I don't think th
On 2011-11-14 16:38 , Ryan Schmidt wrote:
I wasn't sure what would happen when you change the case of the port name like
that. Will users who had qlipper @1.8.2_0 installed get prompted to upgrade to
Qlipper @1.8.2_1? I don't think this is a case we ever deliberately considered,
so if it does
On Nov 13, 2011, at 23:38, Ryan Schmidt wrote:
> On Nov 13, 2011, at 23:06, pva...@macports.org wrote:
>
>> Revision: 87201
>> http://trac.macports.org/changeset/87201
>> Author: pva...@macports.org
>> Date: 2011-11-13 21:06:30 -0800 (Sun, 13 Nov 2011)
>> Log Message:
>> ---
On Nov 13, 2011, at 23:06, pva...@macports.org wrote:
> Revision: 87201
> http://trac.macports.org/changeset/87201
> Author: pva...@macports.org
> Date: 2011-11-13 21:06:30 -0800 (Sun, 13 Nov 2011)
> Log Message:
> ---
> qlipper: buildbot fix (case sensitive paths)
>
> Mod
