procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Move 'package-archives' documentation to emacs manual

Browse source 
* doc/lispref/package.texi (Package Archives): Move documentation
of package-archives variable from here...
* doc/emacs/package.texi (Package Installation): ...to here.
(Bug#76266)
This commit is contained in:
Stefan Kangas 2025-02-13 16:36:40 +01:00
parent 316e47c5af
commit 87a61eba1b
2 changed files with 18 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/emacs/package.texi
View file

@ -407,7 +407,6 @@ package is somehow unavailable, Emacs signals an error and stops
installation.) A package's requirements list is shown in its help installation.) A package's requirements list is shown in its help
buffer. buffer.
@vindex package-archives
By default, packages are downloaded from a single package archive By default, packages are downloaded from a single package archive
maintained by the Emacs developers. This is controlled by the maintained by the Emacs developers. This is controlled by the
variable @code{package-archives}, whose value is a list of package variable @code{package-archives}, whose value is a list of package
@ -418,6 +417,24 @@ name of the package archive directory. You can alter this list if you
wish to use third party package archives---but do so at your own risk, wish to use third party package archives---but do so at your own risk,
and use only third parties that you think you can trust! and use only third parties that you think you can trust!
@defopt package-archives
The value of this variable is an alist of package archives recognized
by the Emacs package manager.
Each alist element corresponds to one archive, and should have the
form @code{(@var{id} . @var{location})}, where @var{id} is the name of
the archive (a string) and @var{location} is its @dfn{base location}
(a string).
If the base location starts with @samp{http:} or @samp{https:}, it
is treated as an HTTP(S) URL, and packages are downloaded from this
archive via HTTP(S) (as is the case for the default GNU archive).
Otherwise, the base location should be a directory name. In this
case, Emacs retrieves packages from this archive via ordinary file
access. Such local archives are mainly useful for testing.
@end defopt
@anchor{Package Signing} @anchor{Package Signing}
@cindex package security @cindex package security
@cindex package signing @cindex package signing

19
doc/lispref/package.texi
View file

@ -309,25 +309,6 @@ hosted on @url{https://elpa.gnu.org, GNU ELPA} and
@url{https://elpa.nongnu.org, non-GNU ELPA}. This section describes @url{https://elpa.nongnu.org, non-GNU ELPA}. This section describes
how to set up and maintain a package archive. how to set up and maintain a package archive.
@cindex base location, package archive
@defopt package-archives
The value of this variable is an alist of package archives recognized
by the Emacs package manager.
Each alist element corresponds to one archive, and should have the
form @code{(@var{id} . @var{location})}, where @var{id} is the name of
the archive (a string) and @var{location} is its @dfn{base location}
(a string).
If the base location starts with @samp{http:} or @samp{https:}, it
is treated as an HTTP(S) URL, and packages are downloaded from this
archive via HTTP(S) (as is the case for the default GNU archive).
Otherwise, the base location should be a directory name. In this
case, Emacs retrieves packages from this archive via ordinary file
access. Such local archives are mainly useful for testing.
@end defopt
A package archive is simply a directory in which the package files, A package archive is simply a directory in which the package files,
and associated files, are stored. If you want the archive to be and associated files, are stored. If you want the archive to be
reachable via HTTP, this directory must be accessible to a web server; reachable via HTTP, this directory must be accessible to a web server;