From: Eric Bavier <ericbavier@centurylink.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 31395@debbugs.gnu.org
Subject: [bug#31395] [PATCH 2/2] gnu: Add snap.
Date: Thu, 10 May 2018 21:32:12 -0500 [thread overview]
Message-ID: <20180510213212.1bd91255@centurylink.net> (raw)
In-Reply-To: <87efijpkng.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On Thu, 10 May 2018 17:58:43 +0200
Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Eric Bavier <ericbavier@centurylink.net> writes:
>
> > It's worse than that. See e.g.
> > https://marc.info/?l=openbsd-ports&m=151973450514279&w=2
> >
> > Many other packages use it because the issue was only brought to light
> > more recently.
>
> I see. Thank you for the reference.
>
> > You don't need to use a git hash at all. If the release is tagged, you
> > can use that in the git-reference commit. E.g. a recent package I
> > made, "ghostwriter", does this.
>
> OK. I used `git-reference'. One difficulty I encountered is the working
> directory when using `git-reference' is non-trivial. I though it would
> put me in the cloned repository, but instead, it left me in an empty
> directory, which is neither the source directory nor the output
> directory. Maybe it should be documented in the manual.
Maybe, yeah. The builders get dropped into the temporary build
directory to start.
>
> Also, note that I couldn't use (which "sh") or (which "xdg-open"), since
> both returned #f. Probably a PATH problem, so I sticked to my previous
> way of finding bash and xdg-open.
Indeed, "which" looks in PATH, so what you've done is fine.
>
> Here is the updated patch. Let me know what you think.
>
LGTM!
Thanks,
`~Eric
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-05-11 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 21:44 [bug#31395] [PATCH 0/2] Add Snap! educational programming language Nicolas Goaziou
2018-05-09 21:46 ` [bug#31395] [PATCH 1/2] gnu: Add js-filesaver Nicolas Goaziou
2018-05-09 21:46 ` [bug#31395] [PATCH 2/2] gnu: Add snap Nicolas Goaziou
2018-05-10 2:36 ` Eric Bavier
2018-05-10 13:10 ` Nicolas Goaziou
2018-05-10 13:47 ` Eric Bavier
2018-05-10 15:58 ` Nicolas Goaziou
2018-05-11 2:32 ` Eric Bavier [this message]
2018-05-11 8:46 ` bug#31395: " Nicolas Goaziou
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180510213212.1bd91255@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=31395@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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/guix.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).