Ian Jackson writes: > > Matt Swift writes: > > > > # ensure proper permissions and ownership > > chown --recursive root:texmf $DIRS > > chmod --recursive ug=rwX,o=rX $DIRS
> Our packaging guidelines say that the things should be owned by > root.root in general. Is there a good reason to use a new group ? No, there is no reason the /usr/lib/texmf tree shouldn't be root:root. The /usr/local/lib/texmf tree is (I assume) entirely up to the sysadmin. I used to use the texmf group because TeX users needed write permissions in /usr/lib/texmf/fonts to build fonts on the fly. Nils's cleaner solution is to put newly built fonts in /var/spool/texmf. Depending on the sysadmin's preferences, new fonts can eventually be moved to the right places in (say) /usr/local/lib/texmf/fonts by hand -- or I think there exist intelligent scripts to deduce the proper TeX Directory Standard location from the font's filename. Such a script might well one day be provided but not enabled on installation.
