Hi,
Andreas Barth <a...@not.so.argh.org> 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.
I have to somewhat disagree there. The maintainer scripts are neigther
variable nor data. They are not-changing executables. One thing that one
could point to though is
| /var/lib : Variable state information
| ...
| /var/lib/<name> is the location that must be used for all distribution
| packaging support. Different distributions may use different names, of
| course.
On the other hand the FHS says:
| /usr/lib : Libraries for programming and packages
|
| Purpose
|
| /usr/lib includes object files, libraries, and internal binaries that
| are not intended to be executed directly by users or shell scripts. [22]
|
| Applications may use a single subdirectory under /usr/lib. If an
| application uses a subdirectory, all architecture-dependent data
| exclusively used by the application must be placed within that
| subdirectory. [23]
The maintainer scripts are "internal binaries that are not intended to
be executed directly by users or shell scripts". So /usr/lib/dpkg/ would
be a valid place to put them.
And I believe the possible argument that /usr is read-only so dpkg may
not write scripts there is not valid. The FHS says for example:
| /var is specified here in order to make it possible to mount /usr
| read-only. Everything that once went into /usr that is written to during
| system operation (as opposed to installation and software maintenance)
| must be in /var.
Clearly it already exempts unpack, install, remove and purge operations
from the restriction from not to write to usr. And dpkg writes/deletes
files in /usr anyway during those operations.
What would prevent storing the maintainer scripts in /usr other than
someone having to write the patch for it?
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
