From: Matthew Jordan <matthewjordandevops@yandex.com>
To: Rodion Goritskov <rodion@goritskov.com>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Creating new package for Guix - newbie's question
Date: Sun, 12 Jun 2016 17:24:37 -0400 [thread overview]
Message-ID: <87y46af6cq.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <5fa1df57607f64fe3ea0890f5ff75674@goritskov.com>
Hi Rodion,
Welcome to Guix!
Here is the fast way;
$ mkdir -p ${HOME}/tmp/packages/gnu/packages
$ export GUIX_PACKAGE_PATH="${HOME}/tmp/packages"
$ mv <package-file>.scm ${HOME}/tmp/packages/gnu/packages
$ guix build <package-name>
If you intend to contribute the package, keep reading.
> OK, that is not really a problem - I tried to create this package
> myself. So, I copied template "hello.scm" from documentation, modified
> it according to compton's build process.
See the following sections/chapters in the Guile Reference Manual;
5 Programming Interface (Page 41)
https://www.gnu.org/software/guix/manual/guix.html#Programming-Interface
6.1 Invoking guix build (Page 75)
https://www.gnu.org/software/guix/manual/guix.html#Invoking-guix-build
8 Contributing (Page 170))
https://www.gnu.org/software/guix/manual/guix.html#Contributing
> Question is - how I can test created package build process?
Here is what I do atm for developing packages.
$ guix environment guix --ad-hoc help2man git strace
$ eval `guix environment guix --ad-hoc --search-paths help2man git
strace`
$ unset GUIX_PACKAGE_PATH
$ export GUIX_BUILD_OPTIONS="--keep-failed --verbosity=3"
$ export BUILD_LOG=${HOME}/tmp/logs/pre-guix-build.log
$ mkdir -p $(dirname ${BUILD_LOG})
Inital setup
$ git clone --recurse git://git.savannah.gnu.org/guix.git
Update
$ git pull --recurse-submodules
Build
$ ./bootstrap
$ ./configure --localstate=/var
$ make
$ make check
Runs in the foreground
optional unless editing damon code
$ sudo ./pre-inst-env guix-daemon --build-users-group=guixbuild
Edit/add code under gnu/packages directory.
$ export GUIX_BUILD_OPTIONS="--keep-failed --verbosity=3"
$ ./pre-inst-env guix build hello &>/dev/stdout &>${BUILD_LOG}
$ ./pre-inst-env guix lint hello
--
Matthew Jordan
Sent with my mu4e
next prev parent reply other threads:[~2016-06-12 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 20:08 Creating new package for Guix - newbie's question Rodion Goritskov
2016-06-12 21:24 ` Matthew Jordan [this message]
2016-06-13 1:19 ` Leo Famulari
2016-06-13 13:37 ` d4n1
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=87y46af6cq.fsf@mailerver.i-did-not-set--mail-host-address--so-tickle-me \
--to=matthewjordandevops@yandex.com \
--cc=help-guix@gnu.org \
--cc=rodion@goritskov.com \
/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).