From: John J Foerch <jjfoerch@earthlink.net>
To: help-guix@gnu.org
Subject: Re: simplest package definition?
Date: Thu, 25 Aug 2016 09:42:47 -0400 [thread overview]
Message-ID: <874m69rmlk.fsf@hecubus.retroj.net> (raw)
In-Reply-To: 87bn0hb57l.fsf@gmail.com
Alex Kost <alezost@gmail.com> writes:
> Alex Kost (2016-08-25 11:19 +0300) wrote:
>
>> John J Foerch (2016-08-25 04:07 +0300) wrote:
>>
>>> Hello Guix,
>>>
>>> What is the simplest possible package definition, to install a single
>>> shell script? If possible, I would like to install it from the
>>> directory in which I'm developing it, and the package definition would
>>> also be in a file in this directory.
>>
>> So you have some dir and 2 files there: "my-shell-script" and
>> "guix.scm", right? If you don't care about shebang (I mean if you have
>> "#!/bin/sh" in the script, it will not be changed to
>> /gnu/store/.../bash), then you can use trivial-build-system.
>
> I've found how to patch shebang staying inside trivial-build-system.
> There is 'patch-shebang' procedure in (guix build utils) module, so all
> is needed is to call it with the proper path (containing bash or another
> shell you use). So the following lines should be added:
>
>> (use-modules
>
> (gnu packages bash)
>
>> (guix gexp)
>> (guix packages)
>> (guix build-system trivial))
>>
>> (let ((script-name "my-shell-script"))
>> (package
>> (name script-name)
>> (version "0.1")
>> (source (local-file (string-append (dirname (current-filename))
>> "/" script-name)))
>> (build-system trivial-build-system)
>> (arguments
>> `(#:modules ((guix build utils))
>> #:builder
>> (begin
>> (use-modules (guix build utils))
>> (let* ((bin-dir (string-append %output "/bin"))
>> (bin-file (string-append bin-dir "/" ,script-name)))
>
> Add inside 'let':
> (bash-bin (string-append (assoc-ref %build-inputs "bash")
> "/bin"))
>
>> (mkdir-p bin-dir)
>> (copy-file (assoc-ref %build-inputs "source") bin-file)
>
> (patch-shebang bin-file (list bash-bin))
>
>> (chmod bin-file #o555)))))
>
> (inputs `(("bash" ,bash)))
>
>> (home-page #f)
>> (synopsis "bla bla")
>> (description "More verbose bla bla")
>> (license #f)))
Thank you so much, this is incredibly helpful, both for doing some odds
and ends that I want to do with my guix system, but also for
understanding packaging better.
--
John Foerch
prev parent reply other threads:[~2016-08-25 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 1:07 simplest package definition? John J Foerch
2016-08-25 8:19 ` Alex Kost
2016-08-25 8:52 ` Alex Kost
2016-08-25 9:03 ` Vincent Legoll
2016-08-25 13:42 ` John J Foerch [this message]
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=874m69rmlk.fsf@hecubus.retroj.net \
--to=jjfoerch@earthlink.net \
--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).