From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "amano.kenji" <amano.kenji@proton.me>, help-gnu-emacs@gnu.org
Subject: Re: package-vc.el should not fetch all commits.
Date: Mon, 04 Mar 2024 14:54:17 +0000 [thread overview]
Message-ID: <877ciixd2e.fsf@posteo.net> (raw)
In-Reply-To: <jwvsf17e7w4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 03 Mar 2024 08:58:20 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> You say there is an intention behind package-vc.el. Do you know the intention?
>
> Yes, it's to install a package in a way that lets you easily hack on it,
> including keeping some local changes, fixing bugs, submitting them
> upstream, merging with some other version of the package, try a new
> branch, ..
Right, but there is no inherent problem in supporting other workflows,
as long as it is reasonably doable. E.g. we could add a user option
that could influence the arguments passed to vc-git-clone, so that one
can inject a --depth=1 argument, and restructure some of the package-vc
functionality to make it reusable for other intents (e.g. better
isolating the "building" from the "installing"), so that other packages
can make use of the logic that prepares manuals or resolves
dependencies. But that should probable be discussed in a bug report,
not here.
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-03-04 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 12:31 package-vc.el should not fetch all commits amano.kenji
2024-03-01 13:33 ` Philip Kaludercic
2024-03-01 22:53 ` amano.kenji
2024-03-02 6:53 ` Philip Kaludercic
2024-03-02 11:46 ` amano.kenji
2024-03-02 14:40 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-03-03 7:53 ` amano.kenji
2024-03-03 13:58 ` Stefan Monnier
2024-03-04 14:54 ` Philip Kaludercic [this message]
2024-03-04 16:30 ` Stefan Monnier
2024-03-05 5:17 ` amano.kenji
2024-03-05 9:42 ` Philip Kaludercic
2024-03-05 15:42 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=877ciixd2e.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=amano.kenji@proton.me \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).