unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "amano.kenji" <amano.kenji@proton.me>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Philip Kaludercic <philipk@posteo.net>, help-gnu-emacs@gnu.org
Subject: Re: package-vc.el should not fetch all commits.
Date: Tue, 05 Mar 2024 05:17:36 +0000	[thread overview]
Message-ID: <Du4XTKxxFJ8pHLCWdkllVBgb1BkjIsSDYP1zV5C5KhA0U4wBnLj7EJFfrkQO0z7Mda68elU6ymxwYrNBL_653fDh2h30BO3ekymnnBL3_lM=@proton.me> (raw)
In-Reply-To: <jwv8r2y7yo7.fsf-monnier+emacs@gnu.org>

I want emacs to update all (VCS) packages.

If package management is outsourced, I can't update all packages with one emacs command.

On Monday, March 4th, 2024 at 4:30 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> > 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.
> 
> 
> But when it comes to installing from arbitrary Git repositories, I think
> a better path would be to provide commands that let `package.el` use
> a local clone, so that users can `git clone` any which way they prefer,
> and then just `M-x package-use-that-clone`.
> 
> It would provide total flexibility for the users without needing endless
> options in our code to handle each and every possible detail.
> 
> 
> Stefan



  reply	other threads:[~2024-03-05  5:17 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
2024-03-04 16:30                 ` Stefan Monnier
2024-03-05  5:17                   ` amano.kenji [this message]
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='Du4XTKxxFJ8pHLCWdkllVBgb1BkjIsSDYP1zV5C5KhA0U4wBnLj7EJFfrkQO0z7Mda68elU6ymxwYrNBL_653fDh2h30BO3ekymnnBL3_lM=@proton.me' \
    --to=amano.kenji@proton.me \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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).