[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:5 rjvbertin@…]:
 > Replying to [comment:4 ryandesign@…]:
 > > There simply seems to be a bug in the nepomuk-core software, or in
 software that uses it (I'm not sure
 > > which), with regard to whether the nepomuk2 directory name should be
 capitalized or not.
 >
 > 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.

 > Remember that this software is developed on case-sensitive systems, so a
 mistake in case in an include file directive is detected immediately.

 Ok.

 > No, what I think is that the nepomuk2 directory contains "C-style"
 header files with a .h extension, while the Nepomuk2 directory contains
 "C++-style" headers, with extension.

 ''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.

 > > The package from the buildbots has the directory name in lowercase.
 >
 > And that's the issue. There has to be a nepomuk2 directory, but also a
 Nepomuk2 directory. If case isn't preserved, these two can end up merged,
 and that won't be detected as long as case is also not used for file name
 resolution.

 The buildslaves have case-sensitive filesystems, so the case is preserved.

 You can examine [http://packages.macports.org/nepomuk-core/?C=M;O=D the
 packages the buildslaves produced] using a command like:
 {{{
 bzcat /tmp/nepomuk-core-4.12.2_0.darwin_10.x86_64.tbz2 | tar tf -
 }}}
 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.

 > In installed most all of KDE from source (using MacPorts) on my 10.6
 system, building and installing to a case-sensitive partition (one more
 reason to install MacPorts off the boot partition, which shouldn't be
 case-sensitive AFAIK).

 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.

 > This worked fine, and gave me the 2 expected header file directories.

 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?

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