Bug#66191: custom: doesn't initialize itself; lacks site-start file
Package: custom
Version: 1.9962-4
custom doesn't properly initialize itself, probably because it
lacks a site-start file. I think this was probably a simple
mistake during the Debianization; the changelog.Debian says this:
custom (1.9962-4) unstable; urgency=low
* Fix qa address.
* custom-init should no longer be necessary---it's now /etc/emacs/site-start.d/50custom.el (closes: bug#65202)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
* File dates should be right now. (closes: bug#59871)
* Fix info stuff. (closes: bug#64646)
* custom is now bugless. I don't want to see it ever again.
-- Michael Alan Dorman <mdorman@debian.org> Tue, 13 Jun 2000 09:07:53 -0400
However, there is no such file in the package:
blp:~(0)$ dpkg -L custom
/.
/usr
/usr/share
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/custom
/usr/share/emacs/site-lisp/custom/cus-edit.el
/usr/share/emacs/site-lisp/custom/cus-face.el
/usr/share/emacs/site-lisp/custom/custom-init.el
/usr/share/emacs/site-lisp/custom/custom.el
/usr/share/emacs/site-lisp/custom/lpath.el
/usr/share/emacs/site-lisp/custom/wid-browse.el
/usr/share/emacs/site-lisp/custom/wid-edit.el
/usr/share/emacs/site-lisp/custom/widget-example.el
/usr/share/emacs/site-lisp/custom/widget.el
/usr/share/emacs/site-lisp/custom/x-overlay.el
/usr/share/doc
/usr/share/doc/custom
/usr/share/doc/custom/copyright
/usr/share/doc/custom/changelog.gz
/usr/share/doc/custom/changelog.Debian.gz
/usr/lib
/usr/lib/emacsen-common
/usr/lib/emacsen-common/packages
/usr/lib/emacsen-common/packages/install
/usr/lib/emacsen-common/packages/install/custom
/usr/lib/emacsen-common/packages/remove
/usr/lib/emacsen-common/packages/remove/custom
This breaks w3-el-e19, at least.
--
"Writing non-free software is not an ethically legitimate activity, so if
people who do this run into trouble, that's good! All businesses based
on non-free software ought to fail, and the sooner the better."
--Richard Stallman
Reply to: