all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: "Ludovic Courtès" <ludo@gnu.org>, Catonano <catonano@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: not tarred source file
Date: Mon, 16 May 2016 08:45:32 +1000	[thread overview]
Message-ID: <5738FC0C.1050506@uq.edu.au> (raw)
In-Reply-To: <878tzb11ll.fsf@gnu.org>

Hi there,

On 16/05/16 06:57, Ludovic Courtès wrote:
> 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.
If it is a single file then I believe it is as simple as deleting the 
unpack phase e.g. fasttree in bioinformatics.scm, I had thought it was 
still good practice not to use the trivial build system where possible 
as it omits some useful defaults.

ben

  reply	other threads:[~2016-05-15 22:45 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
2016-05-15 22:45   ` Ben Woodcroft [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5738FC0C.1050506@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=catonano@gmail.com \
    --cc=help-guix@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.