From: "amano.kenji" <amano.kenji@proton.me>
To: Philip Kaludercic <philipk@posteo.net>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: package-vc.el should not fetch all commits.
Date: Sat, 02 Mar 2024 11:46:21 +0000 [thread overview]
Message-ID: <sdmGtjX6k4ELY3ZkECZWgddLOC9fxzNPylX6qinjvTFOOOTiWoMo6j_kKieMPXx_qRXtX6W7aFZWpH3tme9ET6Z0Qu7A7O-q_ciijId_Ya8=@proton.me> (raw)
In-Reply-To: <87o7bx3z0f.fsf@posteo.net>
I have developed a few small softwares. Unfortunately, I'm trying to graduate software development. I want to stick to software tinkering. I just want to write a few tiny scripts here and there, and I don't know much about emacs lisp.
I don't know the intention behind package-vc.el, but I think it should be flexible enough to keep commit depth at 1 during installation and updates. That's not difficult if you know some git commands. Gentoo linux keeps commit depth at 1 for all package repositories by default.
When people use package-vc.el, in many cases, they have to use it because the desired packages aren't available on emacs package repositories. janet-ts-mode is one example. I just want the latest commit from VCS packages that are not available on emacs package repositories.
If no one wants to make package-vc.el flexible enough to do that, I guess I will just stick to elpaca.
On Saturday, March 2nd, 2024 at 6:53 AM, Philip Kaludercic <philipk@posteo.net> wrote:
> "amano.kenji" amano.kenji@proton.me writes:
>
> > I can contribute patches even if I have only one specific commit or the latest commit.
>
>
> True, my bad I didn't realise that for patches, Git won't have a problem
> with that, even though it seems obvious in retrospect.
>
> A different problem would seem to be updating, or at least a "git pull"
> would download the entire repository.
>
> > That's a bad UX. package-vc.el is the only built-in way to install VCS
> > packages, and there should be a built-in way to install only one
> > commit and update to only one commit.
>
>
> I find these claims difficult, since as mentioned before, the intention
> behind writing package-vc is not just to install a package from a VCS,
> and judging it as such is misguided IMO.
>
> But feel free to work on it, I am not opposed to patches that wouldn't
> violate the fundamental intentions behind package-vc, but I suspect that
> the end-result will be a more advanced version of the command I provided
> below.
>
> Also, if you intend to work on this more seriously, we should move the
> conversation to the bug tracker or private correspondence for the time
> being, where we can discuss details and ideas.
>
> > Gentoo linux achieved one-commit update and one-commit installation
> > for its own package repositories because people did not want
> > repositories to grow in size over time.
>
>
> I am not familiar with Gentoo or why they build from Source (my
> impression has always been that this is partially motivated by a
> performance concern, and the ability to compile optimised executable
> for the current system?).
>
> > On Friday, March 1st, 2024 at 1:33 PM, Philip Kaludercic philipk@posteo.net wrote:
> >
> > > "amano.kenji" amano.kenji@proton.me writes:
> > >
> > > > package-vc-install fetches all commits for a VCS emacs package.
> > > >
> > > > I just want the latest.
> > > >
> > > > package-vc-upgrade and package-vc-upgrade-all should prune everything except the latest commit.
> > > >
> > > > I don't want VCS packages to grow in size over time.
> > >
> > > That is not really what package-vc is about (the intention /is/ to have
> > > the revision history available, so that you can contribute patches).
> > > That being said, if you say you are only interested in packages from
> > > Git, you can use this quick hack:
> > >
> > > --8<---------------cut here---------------start------------->8---
> > >
> > > (require 'package)
> > > (require 'vc-git)
> > > (defun package-install-once-from-vc (url name)
> > > (interactive
> > > (let* ((url (read-string "URL: "))
> > > (name (file-name-base (directory-file-name url))))
> > > (list url (read-string "Name: " name))))
> > > (let* ((tmp (make-temp-file "package" t))
> > > (dir (expand-file-name name tmp)))
> > > (make-directory dir)
> > > (unless (vc-git--out-ok "clone" "--depth" "1" url dir)
> > > (error "Failed to install %s from %s" name url))
> > > (let ((desc (package-install-file dir)))
> > > (message "Package `%s' installed at version %s"
> > > (package-desc-name desc)
> > > (package-version-join
> > > (package-desc-version desc)))
> > > desc)))
> > > --8<---------------cut here---------------end--------------->8---
> > >
> > > This is still missing some of the conveniences of package-vc, such as
> > > building manuals, resolving dependencies, etc. but you could integrate
> > > `package-vc--unpack-1' into the mix to get that to work as well. As is
> > > the case with vc-packages in general, updating is difficult.
> > >
> > > --
> > > Philip Kaludercic on peregrine
>
>
> --
> Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-03-02 11:46 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 [this message]
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
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='sdmGtjX6k4ELY3ZkECZWgddLOC9fxzNPylX6qinjvTFOOOTiWoMo6j_kKieMPXx_qRXtX6W7aFZWpH3tme9ET6Z0Qu7A7O-q_ciijId_Ya8=@proton.me' \
--to=amano.kenji@proton.me \
--cc=help-gnu-emacs@gnu.org \
--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).