From: Joseph Turner <joseph@breatheoutbreathe.in>
To: Philip Kaludercic <philipk@posteo.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: package-vc-install fails to build docs
Date: Fri, 28 Apr 2023 12:42:24 -0700 [thread overview]
Message-ID: <87zg6raisd.fsf@breatheoutbreathe.in> (raw)
In-Reply-To: <87cz3tn7ts.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
> Joseph Turner <joseph@breatheoutbreathe.in> writes:
>> Philip Kaludercic <philipk@posteo.net> writes:
>>> Joseph Turner <joseph@breatheoutbreathe.in> writes:
> You have to look at elpa-admin.el, the "reference interpretation" for
> how package specifications are supposed to work. It is located on a
> separate branch in elpa.git (so that it can be shared between elpa.git
> and nongnu.git).
>
> https://git.savannah.gnu.org/cgit/emacs/elpa.git/tree/elpa-admin.el?h=elpa-admin
>
>> Mind pointing me in the right direction?
>
> Ping me if you need anything else, and submit a bug report with a patch
> as soon as you have something workable. Add a
>
> X-Debbugs-CC: Philip Kaludercic <philipk@posteo.net>
>
> header so that I get notified as well.
In elpa-admin.el, :make and :shell-command are handled by calling bwrap
to sandbox the external processes. Should we do the same thing?
Do you think we should also sandbox makeinfo like elpaa does?
That could be a separate patch.
Best,
Joseph
next prev parent reply other threads:[~2023-04-28 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 5:34 package-vc-install fails to build docs Joseph Turner
2023-04-22 6:07 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-04-22 7:27 ` Philip Kaludercic
2023-04-22 22:56 ` Joseph Turner
2023-04-23 12:37 ` Philip Kaludercic
2023-04-23 16:54 ` Joseph Turner
2023-04-23 18:36 ` Philip Kaludercic
2023-04-23 20:20 ` Joseph Turner
2023-04-24 5:54 ` Philip Kaludercic
2023-04-28 19:42 ` Joseph Turner [this message]
2023-04-28 21:17 ` Philip Kaludercic
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=87zg6raisd.fsf@breatheoutbreathe.in \
--to=joseph@breatheoutbreathe.in \
--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).