GNU bug report logs -
#75383
[BUG] Behavior of package.el with local archives
Previous Next
To reply to this bug, email your comments to 75383 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#75383
; Package
emacs
.
(Sun, 05 Jan 2025 13:34:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Nikolaos Chatzikonstantinou <nchatz314 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 05 Jan 2025 13:34:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello list,
I wanted to set up my own local archive.
From reading (elisp)Creating and Maintaining Package Archives, especially:
> A package archive is simply a directory in which the package files,
and associated files, are stored.
I figured that all I had to do was (add-to-list 'package-archives
'(("my-test-archive" . "~/test"))), and (add-to-list
'package-unsigned-archives "my-test-archive"), and simply include the
single-file .el packages in the ~/test directory, and then a M-x
package-refresh-contents would update the package list and allow me to
install them.
Unfortunately I ran into problems, as the refresh function was failing
to access the local archive, and from digging around a bit the
function `package-refresh-contents' is expecting an "archive-contents"
file.
I'd like to ask, does package.el support local archives? If yes,
should they have an archive-contents file? If not, should the above
info page be modified to be more explicit about the fact that archives
are remote only?
Regards,
Nikolaos Chatzikonstantinou
This bug report was last modified 165 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.