[Pkg-octave-devel] On NOT packaging octave-forge
Thomas Weber
thomas.weber.mail at gmail.com
Fri Jun 8 10:04:21 UTC 2007
Hi,
Am Freitag, 25. Mai 2007 18:14:18 schrieb Rafael Laboissiere:
> * Rafael Laboissiere <rafael at debian.org> [2007-05-24 23:44]:
> IIRC, you have also mentioned a configuration system similar to the
> mods-{enabled,available} in Apache. I like this idea. I just noticed the
> commands a2dismod and a2enmod for configuring Apache. We could provide
> something similar for octave-forge. Even better: a system with which users
> could locally override the system administrator's choices.
Is it acceptable that the user must hand the full path to the package file to
the relevant script?
E.g., in the following situation, the octave-audio package is installed and
enabled (the first line is a symlink to the second, which contains the actual
file)
/etc/octave.d/enabled/octave-audio => /etc/octave.d/available/octave-audio
/etc/octave.d/available/octave-audio
If the user wants to override this, he must call
debian_remove_package("/etc/octave.d/available/octave-audio")
Is this acceptable? Otherwise I would have to check pathes in the function,
which adds cruft to the function.
Thomas
More information about the Pkg-octave-devel
mailing list