On 15/09/14 13:58, Brad King wrote: > On 09/14/2014 10:51 AM, Ximin Luo wrote: >> the following paths will automatically be picked up by CMake: >> >> /usr/(lib/<arch>|lib|share)/cmake/$package/ >> /usr/(lib/<arch>|lib|share)/$package/ >> /usr/(lib/<arch>|lib|share)/$package/(cmake|CMake)/ > > Correct. > >>> http://www.cmake.org/cmake/help/git-master/manual/cmake-packages.7.html > > For reference, a more permanent URL for the current version of the > document is: > > http://www.cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html > >>> That document recommends /usr/lib/cmake as the install location; however >>> that >>> is arguably not compatible with FHS because cmake files are architecture >>> independent, so should be in /usr/share/cmake > > The package configuration files are not always architecture independent. > For some projects they are, for some projects they are not. Sometimes > they contain information derived from the target architecture while > building the project. >
So, what do you think Debian maintainers should do? "Use their discretion" or what? I couldn't find any on my local system, but from the looks of it there are quite a few other packages that install these files, but they all do their own thing and there's no standard: https://packages.debian.org/search?suite=sid&arch=any&searchon=contents&keywords=cmake I tend to think that having a standard obvious place is better - e.g. nodejs packages all go in /usr/lib/nodejs even arch-indep ones because "it could potentially be arch-dependent", but I'm not really the one to make that decision. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
signature.asc
Description: OpenPGP digital signature
