On Friday September 30 2016 03:48:09 Ryan Schmidt wrote:
> > Still: https://bugs.kde.org/show_bug.cgi?id=369554
>
> Thanks.
Also see https://git.reviewboard.kde.org/r/127822/ for a prototype fix I
started working on months ago...
R.
___
macports-dev
> Am 30.09.2016 um 17:30 schrieb Lawrence Velázquez :
>
>> On Sep 30, 2016, at 11:17 AM, Sierk Bornemann wrote:
>>
>> If you were right - why then implementing then case-sensitivity in the
>> first place instead of firstly implementing case-insensitivity?
>
> On Sep 30, 2016, at 11:17 AM, Sierk Bornemann wrote:
>
> If you were right - why then implementing then case-sensitivity in the
> first place instead of firstly implementing case-insensitivity?
I am no expert, but isn't implementing a case-sensitive filesystem
*easier*? The
> On Sep 30, 2016, at 11:10 AM, René J.V. Bertin wrote:
>
>> On Friday September 30 2016 10:10:40 Lawrence Velázquez wrote:
>>
>> So users would have to have this disk image mounted at all times, just
>> in case they ever want to use anything installed by MacPorts?
>
>
> Am 30.09.2016 um 16:28 schrieb Lawrence Velázquez :
>
>> On Sep 30, 2016, at 10:15 AM, Sierk Bornemann wrote:
>>
>>> Am 30.09.2016 um 09:53 schrieb Ryan Schmidt :
>>>
Apple could (and IMHO should) have made case-sensitivity
On Friday September 30 2016 10:10:40 Lawrence Velázquez wrote:
> So users would have to have this disk image mounted at all times, just
> in case they ever want to use anything installed by MacPorts?
Yes, but that can be completely transparent. The image can be mounted at an
appropriate time
> On Sep 30, 2016, at 10:15 AM, Sierk Bornemann wrote:
>
>> Am 30.09.2016 um 09:53 schrieb Ryan Schmidt :
>>
>>> Apple could (and IMHO should) have made case-sensitivity the
>>> default and let everyone come to term with the fact that foo and
>>> Foo are
> On Sep 30, 2016, at 4:44 AM, René J.V. Bertin
> wrote:
>
>> On Friday September 30 2016 02:53:22 Ryan Schmidt wrote:
>>
>> I am not aware of Apple installing files whose names differ only by
>> case; it wouldn't make sense for them to do so, given that the
>> default
> Am 30.09.2016 um 09:53 schrieb Ryan Schmidt :
>> Apple could (and IMHO should) have made case-sensitivity the default and let
>> everyone come to term with the fact that foo and Foo are not the same thing
>> (or add normalising glue code in their highlevel APIs).
>
> On Sep 30, 2016, at 3:39 AM, René J.V. Bertin
> wrote:
>
>> On Thursday September 29 2016 18:21:15 Ryan Schmidt wrote:
>>
>>> But why do it only for ${workpath}; the whole of ${prefix} could be
>>> on a case-sensitive RW dynamically-sized disk image (a sparse
>>> bundle?)
On Friday September 30 2016 03:48:09 Ryan Schmidt wrote:
>> Still: https://bugs.kde.org/show_bug.cgi?id=369554
>
>Thanks.
Let's not hold our breath though. Addressing this issue properly will be very
invasive: lots of dependent code will require patches. And even if the patching
can be done
> On Sep 30, 2016, at 3:44 AM, René J.V. Bertin wrote:
>
> Still: https://bugs.kde.org/show_bug.cgi?id=369554
Thanks.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
On Friday September 30 2016 02:53:22 Ryan Schmidt wrote:
>I am not aware of Apple installing files whose names differ only by case; it
>wouldn't make sense for them to do so, given that the default filesystem is
>case-insensitive and can't accommodate that. If you believe they do install
On Sep 30, 2016, at 2:39 AM, René J.V. Bertin wrote:
> On Thursday September 29 2016 18:21:15 Ryan Schmidt wrote:
>
>>> Ah, good news, because Qt5 and the KF5 frameworks have unfortunately
>>> standardised the behaviour of using capitalised letters in C++ header
>>> filenames.
>>
>> Someone
On Thursday September 29 2016 18:21:15 Ryan Schmidt wrote:
>> Ah, good news, because Qt5 and the KF5 frameworks have unfortunately
>> standardised the behaviour of using capitalised letters in C++ header
>> filenames.
>
>Someone needs to make it clear to them that this is not a good idea. Not
> On Sep 29, 2016, at 5:10 AM, René J.V. Bertin wrote:
>
> On Thursday September 29 2016 07:14:11 MacPorts wrote:
>> #49559: nepomuk-core can't be installed on a case-sensitive system
>
> Hi,
>
>> The new buildbot setup does not show this behavior, so I revbumped
>>
On Thursday September 29 2016 07:14:11 MacPorts wrote:
>#49559: nepomuk-core can't be installed on a case-sensitive system
Hi,
> The new buildbot setup does not show this behavior, so I revbumped
> nepomuk-core in r153339 so that all the packages are correctly rebuilt for
> case-sensitive
17 matches
Mail list logo