From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: New topic: packaging Date: Thu, 14 Feb 2019 15:41:06 +0100 Message-ID: References: <20190213101322.58e3f151@alma-ubu> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:46881) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1guINB-0002fo-75 for guix-devel@gnu.org; Thu, 14 Feb 2019 09:52:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1guICW-0002kV-Ki for guix-devel@gnu.org; Thu, 14 Feb 2019 09:41:21 -0500 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]:38669) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1guICW-0002k3-Eq for guix-devel@gnu.org; Thu, 14 Feb 2019 09:41:20 -0500 Received: by mail-ed1-x533.google.com with SMTP id h58so5197322edb.5 for ; Thu, 14 Feb 2019 06:41:20 -0800 (PST) In-Reply-To: <20190213101322.58e3f151@alma-ubu> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?B?QmrDtnJuIEjDtmZsaW5n?= Cc: Guix-devel 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