From: Brian Cully <bjc@spork.org>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] New package: nspawn-tramp
Date: Sat, 19 Feb 2022 10:27:19 -0500 [thread overview]
Message-ID: <c2ab0522-4667-9351-b2aa-41f1bee12174@spork.org> (raw)
In-Reply-To: <jwvczjivrog.fsf-monnier+emacs@gnu.org>
On 2/19/22 10:05, Stefan Monnier wrote:
> I'd be happy to add it to GNU ELPA, but I have a few questions/comments
> some of which may affect this decision, so I haven't done it yet:
>
> - It's usually spelled "Tramp" rather than "TRAMP", AFAIK.
The info page for it has it spelled as "TRAMP", although the link to it
from the list in the top-level (from "M-x info") has it as "Tramp". I
assume the former is correct given its specificity.
>
> - I suggest you clarify that this is not about Tramp using (internally)
> nspawnd to increase its security. So instead of "allows TRAMP to work
> with containers", I'd say something like "teaches Tramp to access
> nspawnd containers"?
What do you think of "... allows TRAMP access to environments provided
by systemd-nspawn"? I'll admit I'm having a hard time coming up with
language that addresses your concern and sounds natural.
> - `nspawnd-tramp` suggests this adds Tramp support to nspawnd rather than
> the reverse.
I did, initially, call it "tramp-nspawn", but changed it after
reviewing other packages which added container support to TRAMP, like
"docker-tramp" and "lxc-tramp". It doesn't matter much to me, so I went
with what seemed like existing convention.
> - Any reason why you want to have it as a separate package rather than
> add it to Tramp?
TRAMP provides a plugin capability, which is being used by other
packages, and it's already a behemoth. I see no need to include this
directly within TRAMP itself, as its needs are perfectly addressed without.
> - `nspawn-tramp-machinectl-path` does not hold a "path" (like $PATH and
> `load-path`) but a "file name", please follow the GNU convention.
I've renamed the variable to `nspawn-tramp-machinectl-file-name` and
adjusted its documentation.
Thank you for your patch. I've applied them and will push them up to my
repository when the current discussion concludes.
next prev parent reply other threads:[~2022-02-19 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 14:09 [ELPA] New package: nspawn-tramp Brian Cully
2022-02-19 15:05 ` Stefan Monnier
2022-02-19 15:13 ` Andreas Schwab
2022-02-19 15:27 ` Brian Cully [this message]
2022-02-19 18:11 ` Michael Albinus
2022-02-19 20:21 ` Brian Cully
2022-02-20 13:37 ` Michael Albinus
2022-02-20 14:51 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2ab0522-4667-9351-b2aa-41f1bee12174@spork.org \
--to=bjc@spork.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.