From: ludo@gnu.org (Ludovic Courtès)
To: Catonano <catonano@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: not tarred source file
Date: Sun, 15 May 2016 22:57:10 +0200 [thread overview]
Message-ID: <878tzb11ll.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDzSyE-JbT481Y-J53t2EvVmYNrzpuzqqvvctR9F60=EDw@mail.gmail.com> (catonano@gmail.com's message of "Sun, 15 May 2016 22:25:12 +0200")
Hi!
Catonano <catonano@gmail.com> skribis:
> after having successfully packaged (locally) the Zenburn theme and
> Smartparens, I am preparing the package for clojure-mode
>
> But for the first time it happens that the downloaded source code is not
> tarred so tar fails and so does the unpack phase.
>
> How do I instruct the origin object not to attempt untarring my source ?
It’s OK if the ‘origin’ denotes a file that is not a tarball.
However, the build procedure will have to pay attention for that. For
instance, the default sequence of phases of ‘gnu-build-system’ includes
an ‘unpack’ phase, which is inappropriate here:
https://www.gnu.org/software/guix/manual/html_node/Build-Systems.html
There are a couple of examples, e.g., paredit in emacs.scm. Most of
them use ‘trivial-build-system’, which requires explicitly writing the
build/install operations.
HTH!
Ludo’.
next prev parent reply other threads:[~2016-05-15 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 20:25 not tarred source file Catonano
2016-05-15 20:57 ` Ludovic Courtès [this message]
2016-05-15 22:45 ` Ben Woodcroft
2016-05-16 11:02 ` Catonano
2016-05-16 20:04 ` Alex Kost
2016-05-16 20:52 ` Ludovic Courtès
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=878tzb11ll.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=catonano@gmail.com \
--cc=help-guix@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.
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).