RE: [External] : [FR] Provide a way to activate packages automatically for side effect

[Drew Adams <drew.adams@oracle.com>]

> For example, when a package defines a new major mode, it is common to
> modify `auto-mode-alist' by merely having such package installed.

That's common?  It shouldn't be.  Loading/installing
code shouldn't do that, even for a "new major mode".

> This is technically a change in Emacs's editing behavior.

Not just technically - really, practically.

> Another example is when a package adds new features to an existing
> functionality, like ert.el where mere (require 'ert) changes
> fontification in emacs-lisp-mode buffers:
> (add-hook 'emacs-lisp-mode-hook #'ert--activate-font-lock-keywords)

Ditto.

> If one follows "Lisp Coding Conventions" explicitly, the above examples
> can be seen as breaking the conventions.

Not just "can be seen as".  They break the conventions.

> On the other hand, it is very clear that autoloading a major mode is
> justified because otherwise why would user install the relevant package?

Not for the package to guess why.  Up to the user.

> Similar argument 

What's the argument?  Is it just "otherwise why would
a user install..."?  That's not an argument.

> can be made for changing the fontification rules in
> ert.el - if ert library is loaded _by the user_, it is very clear that
> the erc.el features, including fontification, are going to be useful.

It's not clear that that's clear to the user, or that
(more importantly) the user wants those changes made.
___

Just one opinion.  No opinion about whether some more
lax new kind of load function might be useful.