On 2008-04-12 19:23 +0200, Stefano Zacchiroli wrote: > On Sat, Apr 12, 2008 at 06:11:36PM +0200, Sven Joachim wrote: >> Strange, /etc/emacs22/site-start.d is supposed to be a directory and is >> shipped in emacs22-common (on which emacs22 indirectly depends). > > Indeed: > > $ dpkg -L emacs22-common|grep ^/etc > /etc > /etc/emacs > /etc/emacs22 > /etc/emacs22/site-start.d > > But I don't have it nevertheless: > > $ ls /etc/emacs22 > ls: cannot access /etc/emacs22: No such file or directory > > while I do have emacs22 installed. Is it possible that it got removed by > a past package upgrade?
Only by a very recent one (after the installation of emacs22-common), that's why I asked you to send the aptitude and dpkg logs. >> As I said above, /etc/emacs22 is shipped in emacs22-common, and this ... > > Uhm, however, /etc/emacs22 is supposed to be a configuration file Why? Just because it is in /etc? A directory cannot reasonably be a configuration file, IMO. > so I > guess per policy the sysadm is free to do whatever he want with that, > including deleting it. You can also delete the /etc/rc?.d directories, if you want to make your life a bit harder ... > I think you should then consider the case in > which the dir is not there and avoid failing the postinst. In that case you should reassign that bug to emacsen-common, which assumes the existence of /etc/<EMACSFLAVOR> all over the place, see the documentation in /usr/share/doc/emacsen-common/debian-emacs-policy.gz. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
