Re: package-vc.el should not fetch all commits.

[Philip Kaludercic <philipk@posteo.net>]

"amano.kenji" <amano.kenji@proton.me> writes:

> I want emacs to update all (VCS) packages.
>
> If package management is outsourced, I can't update all packages with one emacs command.

I don't think Stefan is arguing to "outsource" package management.  I'd
imagine the idea would be that if you have a any Git repository, you
could just clone it whatever way you want, then M-x
package-use-that-clone the directory and it would be installed and
managed by package.el, which should include the ability to update the
package.

What I am pondering, is if this should be part of package/package-vc, or
if it would be better to make adjustments so that these can be flexibly
extended, and then we could have a "package-git" package on ELPA that
could provide the general interface that Stefan mentioned, and while one
is at it, some auxiliary commands that would streamline common operations.

> 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

-- 
	Philip Kaludercic on peregrine