From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New topic: packaging
Date: Thu, 14 Feb 2019 15:41:06 +0100 [thread overview]
Message-ID: <CAE4v=phHQN9EWQEkXByjxU8HPZDtog9U5Wj-xtBw1_hoWzxO2w@mail.gmail.com> (raw)
In-Reply-To: <20190213101322.58e3f151@alma-ubu>
Hello,
> 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
Yes, I agree to this outline. One possibility if it turns out to be
too much for a single video, is to spilt it up.
Like:
1. building guix from source:
> * 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
2. creating your package:
> * 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
3. checks:
guix lint
guix size
guix build --rounds=2
guix refresh -l (when updating instead of adding)
4. follow up activities:
creating the patch
sending the patch
following it on the issue tracker
incorporating feedback and resending...
WDYT?
In these series we could reference the other parts.
I would perfer to keep as few parts as possible, but this
is one way to split and organize it.
Best regards,
g_bor
next prev parent reply other threads:[~2019-02-14 14:52 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
2019-02-14 14:41 ` Gábor Boskovits [this message]
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='CAE4v=phHQN9EWQEkXByjxU8HPZDtog9U5Wj-xtBw1_hoWzxO2w@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@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.
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).