[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Summary and next steps for (package-initialize)

From: Eli Zaretskii
Subject: Re: Summary and next steps for (package-initialize)
Date: Thu, 24 Aug 2017 21:14:47 +0300

> Date: Thu, 24 Aug 2017 10:44:09 -0700 (PDT)
> From: Drew Adams <address@hidden>
> Cc: address@hidden, address@hidden
> > I don't really understand what this argument is about.  The call to
> > package-initialize does nothing at all, unless you installed some
> > packages with package.el.  So it is still an opt-in feature, because
> > the user must decide to install packages for it to do anything.
> Deciding to "install" a package is somewhat analogous to putting
> a library in your `load-path'.

So that's the flaw in your reasoning: these two are NOT analogous.  A
user who installs a package using package.el does mean to use it.
That's what package.el installation does, that's what it is for.

If one only wants to have the package somewhere on load-path, they
shouldn't use package.el, but instead just download the files, or
clone the Git repository, and then add the directory to load-path.

> That doesn't mean it gets loaded.

Actually, it does.

> Activating a package (`package-initialize') is somewhat analogous
> to loading a library.

No, it isn't.

> Just because a user has installed a package, it doesn't follow
> that s?he wants to always and immediately initialize that package
> for each Emacs session.

Yes, it does mean exactly that.

There are ways to disable an installed package after the installation,
but the default is to make it available when Emacs starts.

So you have some very different use case in mind, not the one we are
talking about here.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]