unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: not tarred source file
Date: Mon, 16 May 2016 23:04:24 +0300	[thread overview]
Message-ID: <87wpmtpy5z.fsf@gmail.com> (raw)
In-Reply-To: <878tzb11ll.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 15 May 2016 22:57:10 +0200")

Ludovic Courtès (2016-05-15 23:57 +0300) wrote:

> 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:

Specifically for this case Federico added 'uncompressed-file-fetch'
method.  Sorry, I forgot to answer at the time, so I answer here.  You
said it's a rare use case¹, but it is actually not.  Many elpa packages
are just single elisp files, so such method can be really useful.  I'm
going to switch our "trivial" emacs packages (paredit, let-alist and
magit-svn) to "emacs-build-system" using this method, if no one will do
it before me.

¹ http://lists.gnu.org/archive/html/guix-devel/2016-01/msg00378.html

>   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.

-- 
Alex

  parent reply	other threads:[~2016-05-16 20:04 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
2016-05-16 11:02     ` Catonano
2016-05-16 20:04   ` Alex Kost [this message]
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=87wpmtpy5z.fsf@gmail.com \
    --to=alezost@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.
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).