If dev-ml/camlp5 is installed, a top-level directory /camlp5 will be created, containing a single file "META" which seems to be a configuration file. This might be a leftover from the "good old MS-DOS times" where it was commonplace to install everything into C:\ as if there were no other directories. But I find it hard to accept this on a *nix System, where established standards like the FHS clearly state that the / root directory is not a place where any single application should put arbitrary files for its specific purposes. camlp5 should place its configuration files to /etc, or /var/run, /var/cache oder /var/lib, but not misuse / for creating a directory for its own purposes there. There are 30000+ packages available for Gentoo, and the / directory would be rather crowded if more packages decided to put a private-purpose directory there. Reproducible: Always Yes, I know this is not a bug per se, provided that violation of the FHS will not prevent an application from running. But is hurts my eye to see that /camlp5 directory every time I have to look at it. If possible, please patch dev-ml/camlp5 to use some different, more standard-compliant directory, such as /etc/camlp5.
yes it is a bug, but not what you may have thought: camlp5 isnt supposed to put that file here, and actually, that file at that location is useless, so there's a problem in its build system / ebuild. $ equery files camlp5 | grep META /usr/lib64/ocaml/camlp5/META ebuild has this: # findlib support insinto "$(ocamlfind printconf destdir)/${PN}" doins etc/META || die "failed to install META file for findlib support" so, most likely cause is that dev-ml/findlib is broken on your system can you try rebuilding it and re-install camlp5 ?
Alexis Ballier wrote > so, most likely cause is that dev-ml/findlib is broken on your system > can you try rebuilding it and re-install camlp5 ? Yes, you are right, that did the trick: The evil file is gone now! :-))) I still don't quite understand why that helped, because I re-emerged that package on 03/30 the last time which was only a couple of days before. Anyway, it helped; problem gone. Thanks a lot & closing the bug!
