From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ffmpeg.
Date: Mon, 02 Dec 2013 13:38:22 +0100 [thread overview]
Message-ID: <87pppftold.fsf@gnu.org> (raw)
In-Reply-To: <20131201145129.GA6641@debian> (Andreas Enge's message of "Sun, 1 Dec 2013 15:51:29 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Sun, Dec 01, 2013 at 12:12:54AM +0100, Ludovic Courtès wrote:
>> The samples wouldn’t really have to be “packaged”: they’d just be an
>> input. For someone using substitutes, the samples are not going to be a
>> problem (because they’ll never be downloaded.) However, it is indeed a
>> problem when building things locally.
>
> Well, so far the only way I have been told to get them is via rsync.
> So one might need to create a .tar(.gz?) from the download.
Not necessarily. It could fetch the directory as is. There could be an
‘rsync-fetch’ method for <origin>, just like we have ‘url-fetch’. (A
little bit of work, but that seems doable, if we want to.)
> And in any case, an input means a package variable, no?
I would rather make it an <origin> (assuming there’s a way to get at an
immutable version of those samples), and it doesn’t need to be bound a
variable:
(define ffmpeg
(package
...
(inputs `(("samples" ,(origin
(method rsync-fetch)
...))))))
Back to the problem at hand: the short-term answer is to add
#:tests? #f with a link to this discussion. The longer term answer
may be to try to run those FATE tests.
WDYT?
Ludo’.
next prev parent reply other threads:[~2013-12-02 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 22:19 [PATCH] gnu: Add ffmpeg Andreas Enge
2013-11-01 11:38 ` Ludovic Courtès
2013-11-01 13:06 ` Andreas Enge
2013-11-01 23:37 ` Ludovic Courtès
2013-11-02 7:47 ` Andreas Enge
2013-11-27 22:50 ` Andreas Enge
2013-11-30 20:44 ` Andreas Enge
2013-11-30 23:12 ` Ludovic Courtès
2013-12-01 14:51 ` Andreas Enge
2013-12-02 12:38 ` Ludovic Courtès [this message]
2013-12-02 17:12 ` Jason Self
2013-12-01 7:06 ` John Darrington
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=87pppftold.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-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 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).