> 1. Move lazy-lock back out of `obsolete'.
Me don't like it. This package is obsolete and we want to phase it out, so
it should be in `obsolete'.
> 2. Reenable scanning of `obsolete' for autoloads.
Sounds good.
> 3. Tell people "you must explicitly load `obsolete/lazy-lock'
> if you want to keep using it, and let the error message serve
> to remind people to switch.
Then why bother distributing it with Emacs at all? We could just as well
tell them to install it separately.
The idea of the `obsolete' directory (the way I understood it) was to have
an equivalent of the `make-obsolete' function: the package is marked as
obsolete and we encourage users not to use it any more, but it is still 100%
backward compatible.
It's good that the `obsolete' is not scanned for custom and finder data: we
don't want to advertize those packages. But not autoloading them is a bit
excessive I think. I'd rather remove autoload cookies on a case by
case basis.
Stefan
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
