From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 37857@debbugs.gnu.org
Subject: [bug#37857] [PATCH] guix: svn: Allow dropping externals
Date: Tue, 22 Oct 2019 18:10:59 +0200 [thread overview]
Message-ID: <87d0eozros.fsf@gnu.org> (raw)
In-Reply-To: <20191021215538.60675430@sybil.lepiller.eu> (Julien Lepiller's message of "Mon, 21 Oct 2019 21:55:38 +0200")
Hi Julien,
Julien Lepiller <julien@lepiller.eu> skribis:
>>From 0ac412a3c912b2fe7ebd05d178120db50d47184e Mon Sep 17 00:00:00 2001
> From: Julien Lepiller <julien@lepiller.eu>
> Date: Mon, 21 Oct 2019 21:48:31 +0200
> Subject: [PATCH] guix: svn: Allow dropping externals.
>
> * guix/build/svn.scm (svn-fetch): Allow to ignore externals.
> * guix/svn-download.scm (svn-reference, svn-multi-reference): Add
> fetch-externals? field.
Nice.
For consistency with git-download.scm & co., what about calling the
parameter and the field ‘recursive?’ rather than ‘fetch-externals?’?
> (define-record-type* <svn-reference>
> svn-reference make-svn-reference
> svn-reference?
> - (url svn-reference-url) ; string
> - (revision svn-reference-revision) ; number
> - (user-name svn-reference-user-name (default #f))
> - (password svn-reference-password (default #f)))
> + (url svn-reference-url) ; string
> + (revision svn-reference-revision) ; number
> + (fetch-externals? svn-reference-fetch-externals? (default #t))
Do you know of packages that rely on externals?
It’d be great to eventually default to #f, but for that we’d need to
check every package that uses ‘svn-fetch’ (notably all the TeX Live
packages.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-10-22 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 19:55 [bug#37857] [PATCH] guix: svn: Allow dropping externals Julien Lepiller
2019-10-22 16:10 ` Ludovic Courtès [this message]
2019-10-23 21:34 ` bug#37857: " Julien Lepiller
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=87d0eozros.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37857@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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/guix.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.