Bug#332264: tex-common: permission-handling of ls-R files is one-way
Norbert Preining <preining@logic.at> wrote:
> I have done:
> . changed the templates description
> . removed the unnecessary templates (groupperm userperm)
> . dh_unregister the unnecessary templates
> . removed the transfer of tetex settings to tex-common
> (why did we do it at all? debconf is not a registry! ;-)
> . changed config.in and postinst.in to work with our policy
Thank you very much.
> Here is the select function (I don't send the common.functions):
> select_lsrfile() {
> case $1 in
> main) LSR=$TEXMFSYSVAR/ls-R-TEXMFMAIN ;;
> var) LSR=$TEXMFSYSVAR/ls-R ;;
> cache) LSR=/var/cache/fonts/ls-R ;;
> *) echo "This should not happen: Don't know how to set this! $lsr" ;;
*) echo "This should not happen: Don't know how to set this! $1" ;;
> One last question: In the postinst at the end there is
> db_get tex-common/groupname || true
> LSRGROUP="$RET"
> if [ -n $LSRGROUP ] ; then
> for i in $truegwritefiles ; do
> lsr=`select_lsrfile $i`
> chgrp -v $LSRGROUP $lsr 2>/dev/null || true
> done
> fi
>
> I have eliminated the grp call. But should we also eliminate the || true?
> What happens if the user types in an unexistent group
The cool version (we could save that idea in a comment) would be to
check (in config) whether the chosen group really exists, and ask in a
loop until an existing group is given. The less cool, but easy version
is maybe to just remove the 2>/dev/null, but not the || true - I don't
know whether this really warrants a complete failure of installation.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Reply to: