From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New topic: packaging
Date: Wed, 13 Feb 2019 10:13:22 +0100 [thread overview]
Message-ID: <20190213101322.58e3f151@alma-ubu> (raw)
In-Reply-To: <CAPNLzUNK9-CCm5jJCtehyxp7KfAuYFUw5VJA7CJitU62PMvo3Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
On Mon, 11 Feb 2019 11:38:21 -0300
Laura Lazzati <laura.lazzati.15@gmail.com> wrote:
> Hi Guix again!
>
> Another topic is about showing how to package.
>
> Gábor suggested maybe using my experience about creating a new R
> package.
>
> My idea is to show how to look for a package that is not packaged,
> package it and the workflow for testing it with git am and send it to
> the patches list. WDTY?
Aggreed on R: There is the importer to show, and R-packages are usually
easy to go.
We have the rough idea of steps to take in the manual. Point people to
the right chapter here.
Then it would involve the whole things:
* git clone ...
* go into guix directory
* Enter the environment:
guix environment guix
--> Explain what happens here and what's so cool about it.
* ./bootstrap
* ./configure --localstatedir=/var
* make
* Then the import begins:
* ./pre-inst-env guix import ...
* [hack file, using emacs, maybe ./pre-inst guix edit new-package]
* ./pre-iinst-env guix build new-package
* Check:
./pre-inst-env guix lint new-package
* Finally:
Commit, take care of the correct commit messsages
* git format-patch and maybe git send-email
This is a lot for even a simple R package but I don't see how/where we
could leave out steps without confusing people.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-02-13 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 14:38 New topic: packaging Laura Lazzati
2019-02-11 15:49 ` znavko
2019-02-13 3:03 ` Laura Lazzati
2019-02-13 9:13 ` Björn Höfling [this message]
2019-02-14 14:41 ` Gábor Boskovits
2019-02-14 14:55 ` Laura Lazzati
2019-02-17 9:02 ` swedebugia
2019-02-18 21:16 ` Björn Höfling
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=20190213101322.58e3f151@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).