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: Mon, 14 Nov 2022 11:28:47 +0000 [thread overview]
Message-ID: <87cz9p3hcg.fsf@posteo.net> (raw)
In-Reply-To: <60289282-1604-4239-BB4F-0D46F06CA39F@gmail.com> (Yuan Fu's message of "Tue, 8 Nov 2022 01:51:54 -0800")
Yuan Fu <casouri@gmail.com> writes:
> I’m happily trying out package-vc and hoping it can replace
> my home-brew install-from-source package!
> The docstring of package-vc-selected-packages mentions
> package-vc-archive-spec-alist but I can’t seem to find it anywhere.
I have been preparing a few changes on scratch/package-vc-fixes, I
believe that the issues you mention have been resolved there.
> 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.
Yuan Fu <casouri@gmail.com> writes:
> CC Phillip since he probably didn’t see this.
You are right, sorry about that.
next prev parent reply other threads:[~2022-11-14 11:28 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 [this message]
2022-11-15 18:29 ` Yuan Fu
2022-11-15 18:58 ` Philip Kaludercic
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cz9p3hcg.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).