binary nepomuk-core package corruption due to case-insensitive filesystem

[RJVB (René Bertin)]

This is a follow-up on ticket:37968 , because I have bumped into the same build failure mentioned there.

As mentioned in the original issue, installing nepomuk-core on a case-insensitive filesystem mixes up the (C++) Nepomuk2 and nepomuk2 (C?) header directories. HFS+ being case-preserving this indicates an issue in the install or in the packaging procedure. I build nepomuk-core from source on a case-sensitive FS and the resulting header tree was as expected and intended, which makes me suspect packaging procedure.

I don't know why the original ticket was closed as "invalid", but I'd really like to make a case for the use of case-sensitive filesystems on the buildbots even if the default on OS X is case-insensitive. This maps better to the origin of the majority of projects. Any adaptations required to allow installation on case-insensitive filesystems will work fine on a case-sensitive filesystem while mix-ups of the sort described in the original issue are prevented automatically.

[mf2k (Frank Schima)]

In the future, please Cc the port maintainers (port info --maintainers nepomuk-core).