From: Joseph Turner <joseph@breatheoutbreathe.in>
To: monnier@iro.umontreal.ca
Cc: Adam Porter <adam@alphapapa.net>,
Philip Kaludercic (Emacs) <philipk@posteo.net>,
Emacs Devel Mailing List <emacs-devel@gnu.org>
Subject: Re: [package-vc] Consider cleaning up files from install process
Date: Wed, 04 Oct 2023 01:22:05 -0700 [thread overview]
Message-ID: <87sf6q3i36.fsf@breatheoutbreathe.in> (raw)
> > In other words, the way package-vc-install currently works leaves me
> > vulnerable to this scenario:
> >
> > 1. I use package-vc-install to install one of my packages from its local
> > repository directory.
> > 2. I check out a feature branch of that package to work on a new feature,
> > saving some files but not loading any of the changed code.
> > 3. I restart Emacs (e.g. maybe I shut down the system and turned it back on
> > the next day).
> > 4. That work-in-progress feature branch of my package gets loaded into
> > Emacs automatically (which may be entirely broken, being a WIP).
> Not sure why you consider that a problem. That's the whole purpose of
> installing straight from the VCS rather than from a tarball.
> If you don't want your Emacs to use that work-in-progress feature
> branch, then work on it elsewhere than in the VCS clone that was created
> specifically to be used in-place.
> E.g. use `git worktree`.
> > Philip, would you be willing to consider switching to that model for
> > package-vc-install, or offering it as an option?
> The option already exists, it's called `git worktree` :-)
I had not considered `git worktree` as a solution. Very neat.
> Switching to "that model" wholesale would prevent the current use where
> you can edit the *live* files.
Thank you!
Joseph
next reply other threads:[~2023-10-04 8:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 8:22 Joseph Turner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 8:31 [package-vc] Consider cleaning up files from install process Joseph Turner
2023-10-04 15:23 ` Philip Kaludercic
2023-10-04 18:54 ` Joseph Turner
2023-10-06 9:00 ` Philip Kaludercic
2023-10-04 8:11 Joseph Turner
2023-09-19 7:24 Joseph Turner
2023-09-19 9:03 ` Philip Kaludercic
2023-09-19 12:19 ` Adam Porter
2023-09-19 13:50 ` Philip Kaludercic
2023-09-19 14:34 ` Adam Porter
2023-09-20 8:13 ` Philip Kaludercic
2023-10-07 7:52 ` Adam Porter
2023-10-07 13:31 ` Philip Kaludercic
2023-09-20 12:13 ` Stefan Monnier via Emacs development discussions.
2023-09-20 12:08 ` Stefan Monnier via Emacs development discussions.
2023-09-20 12:03 ` Stefan Monnier via Emacs development discussions.
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=87sf6q3i36.fsf@breatheoutbreathe.in \
--to=joseph@breatheoutbreathe.in \
--cc=adam@alphapapa.net \
--cc=emacs-devel@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.
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).