--- Begin Message ---
Hi Frank, hi all!
(Taking off various bugs)
On Don, 14 Dez 2006, Frank Küster wrote:
> Consequently, the files that are now below /etc/texmf/texlive could be
> at their "ordinary" places instead,
>
> /etc/texmf/texlive/dvips/config.ps -> /etc/texmf/dvips/config
[...]
> Maybe shared configuration files are not a bad idea, I should look up
> the Debian Policy about that.
Sound bad:
---
10.7.4. Sharing configuration files
-----------------------------------
Packages which specify the same file as a `conffile' must be tagged as
_conflicting_ with each other. (This is an instance of the general
rule about not sharing files. Note that neither alternatives nor
diversions are likely to be appropriate in this case; in particular,
`dpkg' does not handle diverted `conffile's well.)
The maintainer scripts must not alter a `conffile' of _any_ package,
including the one the scripts belong to.
If two or more packages use the same configuration file and it is
reasonable for both to be installed at the same time, one of these
packages must be defined as _owner_ of the configuration file, i.e.,
it will be the package which handles that file as a configuration
file. Other packages that use the configuration file must depend on
the owning package if they require the configuration file to operate.
If the other package will use the configuration file if present, but
is capable of operating without it, no dependency need be declared.
If it is desirable for two or more related packages to share a
configuration file _and_ for all of the related packages to be able to
modify that configuration file, then the following should be done:
1. One of the related packages (the "owning" package) will manage
the configuration file with maintainer scripts as described in
the previous section.
2. The owning package should also provide a program that the other
packages may use to modify the configuration file.
3. The related packages must use the provided program to make any
desired modifications to the configuration file. They should
either depend on the core package to guarantee that the
configuration modifier program is available or accept gracefully
that they cannot modify the configuration file if it is not.
(This is in addition to the fact that the configuration file may
not even be present in the latter scenario.)
Sometimes it's appropriate to create a new package which provides the
basic infrastructure for the other packages and which manages the
shared configuration files. (The `sgml-base' package is a good
example.)
--------------------
So we have three options:
- Move all the stuff to tex-common
- eliminate tetex and move all the stuff from /etc/texmf/texlive/ to
/etc/texmf
- leave it as it is
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Università di Siena
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
PAPWORTH EVERARD (n.)
Technical term for the third take of an orgasm scene during the making
of a pornographic film.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-tex-maint-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
--- End Message ---