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

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

 I think one could also argue the other way around, that nepomuk has been
 conceived for a *nix desktop, and that it's not up to them but up those
 who want to use the software on a case-insensitive system to make that
 work...
 I'll see if there's conscious choice behind what you call a design error,
 but do realise that we're not talking about a set of project-internal
 headerfiles here, but headers included probably by anything using nepomuk
 ...

 > 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 think that in fact the explanation was staring in our faces. You told me
 that the binary tarballs on packages.macports.org had all headers in a
 single nepomuk2 directory. I double-checked that's indeed the case, but
 now look at what I have in the binary tarball that must have been the
 result of the install-from-source build (one can wonder why the file
 wasn't regenerated today, but that's a different question):

 {{{
 drwxr-xr-x root/admin        0 2014-03-10 15:54
 ./opt/local/include/Nepomuk2/
 drwxr-xr-x root/admin        0 2014-03-10 15:54
 ./opt/local/include/nepomuk2/
 [...]
 -rw-r--r-- root/admin     2583 2013-12-10 19:10
 ./opt/local/include/nepomuk2/createresourcejob.h
 -rw-r--r-- root/admin       43 2013-12-10 19:10
 ./opt/local/include/Nepomuk2/CreateResourceJob
 }}}

 so, this tarball was likely created by simply archiving everything in the
 destroot folder.

 Now if I unpack this tarball on a case-insensitive filesystem, all my
 nepomuk2 and Nepomuk2 headers end up in a single directory — in this case
 in the Nepomuk2 directory.

 And that leads me to wonder if the tarballs over on packages.macports.org
 have not by any chance been unpacked and then regenerated on a case-
 insensitive filesystem. You claim that the buildslaves use case-sensitive
 filesystems ... but does that include the root, and thus places like /tmp
 and $TMPDIR ?

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