[MacPorts] #42904: binary nepomuk-core package corruption due to case-insensitive filesystem

[MacPorts]

#42904: binary nepomuk-core package corruption due to case-insensitive filesystem
---------------------------+---------------------
  Reporter:  rjvbertin@…   |      Owner:  nicos@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.2.1
Resolution:                |   Keywords:
      Port:  nepomuk-core  |
---------------------------+---------------------

Comment (by rjvbertin@…):

 Replying to [comment:6 ryandesign@…]:
 > > No, I don't think there's a bug.
 >
 > Well, you claim there is a bug: you've filed this ticket. And I'm
 claiming it's not a MacPorts bug.

 When I filed the ticked I thought that the buildsystem was probably not
 case-sensitive, as that would explain the issue, and made a case for using
 case-sensitive filesystems.


 > ''If'' that is what they've done -- if they intend for there to be two
 different items in the same directory whose names differ only by case --
 then that is
 > unsupportable and that is the bug you should report to them. However,
 thus far, I see no evidence that that is the case.

 It really looks like that. On my Linux boxes I have /usr/include/nepomuk2
 and /usr/include/Nepomuk2 with different, non-overlapping contents.

 > As you can see, there is no directory Nepomuk2. If there should be one,
 then the build system is to blame. As you can see by looking at
 >[browser:trunk/dports/kde/nepomuk-core/Portfile the Portfile], we're not
 doing anything special.

 Hmmm, and elsewhere? Is there something we could learn from doing a
 command like

 port -k destroot -s nepomuk-core

 ?

 > I know of no reason why the boot partition couldn't be case-sensitive,
 only that using a case-sensitive filesystem on OS X is nonstandard and you
 >may therefore be more likely to run into problems because of developers
 who did not test under that configuration.

 The OS itself isn't made for it, and is likely to run into "file not
 found" errors because of it. Very likely because of those last few words
 above ...

 > If that's indeed true, it would be interesting to know how your build
 differs from ours. Are you supplying additional configure flags,
 environment
 > variables, etc?

 From what I remember, I simply did a port install kde4-runtime . When I
 set out it was really to see how far I'd get, so I certainly didn't start
 doing special things!

 R.

-- 
Ticket URL: <https://trac.macports.org/ticket/42904#comment:7>
MacPorts <http://www.macports.org/>
Ports system for OS X