This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Packaging and directories (off topic)
- From: "Jonathan S. Shapiro" <shap at eros-os dot org>
- To: newlib at sources dot redhat dot com
- Date: Sat, 01 Oct 2005 16:21:49 -0400
- Subject: Packaging and directories (off topic)
This is not, strictly speaking, a newlib question, but it is something
that many cross tool builders need to deal with and I would appreciate
advice. If I knew of a mailing list that was more appropriate for cross
tool issues, I would post there instead.
I'm putting together RPMS for a cross tool chain. I've got a workable
onfiguration at this point, and I'm trying to nail down two packaging
issues. The main one concerns directories.
I would like it to be the case that all directories are cleaned up when
the respective packages are removed. Many of the directories are clearly
unique to a package, and there is no real problem with these, but a
directory like
${sysroot}/usr/include/
isn't exclusively "owned" by any one package. I can either attribute
such directories to the first package that creates them, or I can
introduce a dedicated package that is responsible for installing (and
removing) these "standard" directories.
Is there a common practice for how to handle this sort of thing?
Thanks
shap