[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: Add TuxGuitar.
From: |
Ricardo Wurmus |
Subject: |
Re: [PATCH] gnu: Add TuxGuitar. |
Date: |
Sun, 20 Sep 2015 17:39:30 +0200 |
Ludovic Courtès <address@hidden> writes:
> Ricardo Wurmus <address@hidden> 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 in Thread] |
Current Thread |
[Next in Thread] |
- Re: [PATCH] gnu: Add TuxGuitar.,
Ricardo Wurmus <=