From: raingloom <raingloom@riseup.net>
To: 白い熊 <help-guix_gnu.org@sumou.com>
Cc: help-guix@gnu.org
Subject: Re: Package definition - argument, fix for wrong file format before unpack
Date: Sat, 21 May 2022 22:29:10 +0200 [thread overview]
Message-ID: <20220521222910.07a43915@riseup.net> (raw)
In-Reply-To: <3eceaea9454f82f2d8c28af880f82ecb@sumou.com>
On Sat, 21 May 2022 20:16:06 +0200
白い熊 <help-guix_gnu.org@sumou.com> wrote:
> Hello everyone:
>
> I'm trying to build some old apps - one of them is an emacs package
> only available now via the archive.org Wayback machine.
>
> The problem is though that the download is an xxxx.tar.gz file in
> name - in fact it is really only a tar archive. So guix build fails
> with wrong file format error. Concretely - it is this file:
> https://web.archive.org/web/20110104020844/http://taiyaki.org/elisp/mell/src/mell-1.0.0.tar.gz
>
> I think I should add some "(arguments" lines in the package recipe -
> replacing the unpack phase? However not sure exactly how - am
> searching but haven't found any examples fixing for such a problem.
>
> Could someone advise me - how to specify the file should be unpacked
> as really just a tar archive so that the build can then proceed?
>
> Many thanks.
>
If I remember correctly, the source should get passed as part of the
inputs alist? Try this:
`(replace 'unpack (lambda args (display args)))`
And look at what arguments it gets passed. The store path of the
tarball should be right there.
next prev parent reply other threads:[~2022-05-21 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 18:16 Package definition - argument, fix for wrong file format before unpack 白い熊
2022-05-21 20:29 ` raingloom [this message]
2022-05-21 21:55 ` 白い熊
2022-05-21 22:15 ` Tobias Geerinckx-Rice
2022-05-21 22:31 ` Tobias Geerinckx-Rice
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=20220521222910.07a43915@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=help-guix_gnu.org@sumou.com \
/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.
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).