From: Philip Kaludercic <philipk@posteo.net>
To: Yuan Fu <casouri@gmail.com>
Cc: 59120@debbugs.gnu.org
Subject: bug#59120: 29.0.50; [package-vc] Nowhere to find package-vc-archive-spec-alist
Date: Tue, 15 Nov 2022 18:58:08 +0000 [thread overview]
Message-ID: <87mt8s59kv.fsf@posteo.net> (raw)
In-Reply-To: <C9741558-DCAB-43CA-8698-EF607626B79A@gmail.com> (Yuan Fu's message of "Tue, 15 Nov 2022 10:29:47 -0800")
Yuan Fu <casouri@gmail.com> writes:
>>> More over, it would be nice if the documentation of package-vc-install
>>> (docstring or manual) can explain how do I specify the branch when
>>> Using package-vc-install. From what I can see you can only specify the url
>>> and revision.
>>
>> There is no explicit way to do this right now, besides switching to a
>> different branch after checking out the repository.
>>
>> The only other thing you can do is provide a package specification, as
>> documented in `package-vc-selected-packages'. That has a :branch
>> property.
>
> I wonder if I can define my own package archive, so that I can control
> everything easily, without setting up a full-blown archive with
> tarballs and a server. Because I’m not going to download any tarballs
> from the archive, and will only use package-vc-install on this
> personal archive. IOW a package archive that only provide package
> specs. Is that possible?
It should possible, you would have an empty archive-contents and an
elpa-packages.eld file containing all the specifications. I haven't
tried it out though, so something might be broken -- but nothing that
can't be fixed.
next prev parent reply other threads:[~2022-11-15 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 9:51 bug#59120: 29.0.50; [package-vc] Nowhere to find package-vc-archive-spec-alist Yuan Fu
2022-11-14 9:18 ` Yuan Fu
2022-11-14 11:28 ` Philip Kaludercic
2022-11-15 18:29 ` Yuan Fu
2022-11-15 18:58 ` Philip Kaludercic [this message]
2022-11-27 14:05 ` Philip Kaludercic
2022-11-27 21:46 ` Yuan Fu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mt8s59kv.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=59120@debbugs.gnu.org \
--cc=casouri@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.