tag 21941 wontfix thanks [ Goswin, removing the wontfix tag is not something for you to decide. ]
On Sun, 2010-12-26 at 16:56:49 +0100, Andreas Barth wrote: > re usage of /var: > ~~~~~~~~~~~~~~~~ > dpkg puts the package data into /var/lib/dpkg/info. This includes the > list of files, the list of conffiles, templates, md5sums and also the > maintainer scripts of each package. > > According to FHS: > | /var contains variable data files. This includes spool directories and > | files, administrative and logging data, and transient and temporary > | files. > re /var/lib: > | This hierarchy holds state information pertaining to an application or > | the system. > > The usage of /var/lib/dpkg matches that description IMHO. ... as those files are clearly state for dpkg. Those scripts are variable in the sense that they might appear, disappear, or change during a dpkg run. So the location seems perfectly fine to me. It's more relevant though the snippet Goswin pasted: | /var/lib/<name> is the location that must be used for all distribution | packaging support. Different distributions may use different names, of | course. The same equivalent path rpm is using for example. And thus I don't see the point in changing the current location. Even if the /usr/lib location could be interpreted and argued as valid too, I'd not see the point in changing it, given the coding and transition work involved, susceptible to system breakage, and unfortunately also because there are programs out there which rely on those paths (which could be solved with symlinks, but then we'd be getting into really ugly territory, for no really good reason). But mostly given the solution below. > possible ways for /var to be no-exec > ==================================== [...] > per local admin > 4. remount /var with exec > ~~~~~~~~~~~~~~~~~~~~~~~~~ > AFAICS there is no option within dpkg (or not documented) to always > execute commands prior to an dpkg "writing" invocation (while there is > within apt). It might make sense to remount /var with exec in case > it's noexec before running any scripts. > I think adding hooks for dpkg to run scripts pre-/post-changing > requests (e.g. configure, remove, install, ...) might make sense. There's already the invoke hooks (see man dpkg), present since 1.15.4, which allow just that. thanks, guillem -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
