From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add TuxGuitar.
Date: Sun, 20 Sep 2015 17:39:30 +0200 [thread overview]
Message-ID: <87fv295cct.fsf@elephly.net> (raw)
In-Reply-To: <87h9s7zy4z.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> The
>> SWT tarball does include jars but these are binaries of the library.
>> The package recipe ignores them and only works on the sources in src.zip
>
> OK. What about adding a snippet that removes all these jars anyway,
> mostly “to be safe” and to not convey the impression that we’re bundling
> pre-built binaries?
I just tried to do this, but I get stuck as Guix seems to think that the
sources are located in the “about_files” directory:
~~~~~~
...
Archive: /gnu/store/lkk22318a7mrj5m7mx0s574raa4kj7h0-swt-4.4.2-gtk-linux-x86.zip
creating: about_files/
inflating: .classpath
inflating: .project
inflating: about.html
inflating: about_files/IJG_README
inflating: about_files/lgpl-v21.txt
inflating: about_files/mpl-v11.txt
inflating: about_files/mpl-v20.txt
inflating: about_files/webkit-bsd.txt
inflating: src.zip
inflating: swt-debug.jar
inflating: swt.jar
source is under 'about_files'
...
~~~~~~
In fact, the sources are in the “src.zip” archive. Currently, I just
replace the “unpack” phase to take care of this, but I don’t know how to
fix this in a snippet. I’d like to repackage just the contents of
“src.zip” as the source tarball, but ‘patch-and-repack’ doesn’t make it
easy.
~~ Ricardo
prev parent reply other threads:[~2015-09-20 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 4:34 [PATCH] gnu: Add TuxGuitar Ricardo Wurmus
2015-04-21 16:02 ` Ludovic Courtès
2015-04-21 19:49 ` Ricardo Wurmus
2015-04-22 20:49 ` Ludovic Courtès
2015-04-23 7:06 ` Ricardo Wurmus
2015-09-20 15:39 ` Ricardo Wurmus [this message]
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=87fv295cct.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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/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.