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

MacPorts noreply at macports.org
Sat Mar 22 05:39:10 PDT 2014


#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: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. Remember that this software is developed
 on case-sensitive systems, so a mistake in case in an include file
 directive is detected immediately.

 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.

 I've made similar distinctions myself in the past, playing with filename
 case to introduce subtle variations. Not a good idea as I learned.

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

 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). This worked fine, and gave me the 2 expected header
 file directories.

 So I don't think there's an error neither in the source code nor in the
 Portfile/build system ... except possibly when the build/packaging chain
 contains a case-insensitive (potentially non-preserving) filesystem
 somewhere.

 The question is indeed if and how the devs support installation on ... MS
 Windows (with its filesystems that are by default case insensitive and non
 preserving)!

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


More information about the macports-tickets mailing list