[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 ryandesign@…):

 Replying to [comment:7 rjvbertin@…]:
 > > ''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.

 If that's true, then please report that design error to the developers so
 that they can fix it. We obviously cannot accommodate such a scenario in a
 package manager designed for use on an OS where case-insensitive
 filesystems are the norm.

 > > 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 don't think so. You can run that on your case-sensitive filesystem if
 you like and examine the contents of the work/destroot directory, but it
 should be identical to what gets installed by the port and reported by
 "port contents nepomuk-core", since the process of getting the contents of
 the destroot into the archive is handled by MacPorts base automatically
 and individual Portfiles don't have any say in it.

 > > 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,

 Sure it is.

 > and is likely to run into "file not found" errors because of it. Very
 likely because of those last few words above ...

 Only in poorly-constructed third-party software.

 > > 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!

 You said you built from source, and I assumed you meant by hand, so I was
 wondering what configure flags and environment variables you had given
 when doing that.

 Or did you mean that you had built from source using MacPorts? If so,
 again we need to figure out what's different between your system and the
 buildbot's system to account for the difference.

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