From: Catonano <catonano@gmail.com>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: help-guix@gnu.org
Subject: Re: not tarred source file
Date: Mon, 16 May 2016 13:02:30 +0200 [thread overview]
Message-ID: <CAJ98PDwpyXq1RGYPaE2JiOyb_C=HwLcdxyGMFh8H5okRRH80+Q@mail.gmail.com> (raw)
In-Reply-To: <5738FC0C.1050506@uq.edu.au>
[-- Attachment #1: Type: text/plain, Size: 2829 bytes --]
Ben and Ludovic,
thank you
2016-05-16 0:45 GMT+02:00 Ben Woodcroft <b.woodcroft@uq.edu.au>:
> 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.
>>
>
Ludo, in fact, for my Zenburn theme package, I copied the build code from
the paredit package.
But then I noticed that other Emacs modules used the Emacs build system
instead of the trivial one.
> 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.
>
That's what I thought too. If there's a build system made on purpose for
Emacs modules, then that's the right module for me.
Now, Ben, I copied from the fasttree package for my clojure mode and this
is the relevant bit
(build-system emacs-build-system)
(inputs `(("emacs" ,emacs-no-x)))
(arguments
`(#:phases
(modify-phases %standard-phases
(delete 'unpack))))
Now the build succeeds but 2 weird thing happen:
1. in .guix-profile/share/emacs/site-lisp/guix.d/ there's a clojure mode
autoloads file but there's NO clojure-mode file !
So I would say that the build wasn't so successful !
2. During the build lots of packages were downloaded, including Emacs.
But I explicitly indicated emacs-no-x in the recipe.
This didn't happen with Smartparens (that also used the Emacs build
system).
It's as if modifying the standard phases messed up the build process
Now, I could easily welcome Ludo's suggestion to use the trivial build
system as I did with the Zenburn theme
But I'd like to understand.
If there's anyone wiling to inspect my clojure-mode recipe, I can paste it
on pastebin or somewhere else.
[-- Attachment #2: Type: text/html, Size: 4199 bytes --]
next prev parent reply other threads:[~2016-05-16 11:02 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 [this message]
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='CAJ98PDwpyXq1RGYPaE2JiOyb_C=HwLcdxyGMFh8H5okRRH80+Q@mail.gmail.com' \
--to=catonano@gmail.com \
--cc=b.woodcroft@uq.edu.au \
--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).