From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Packagers tutorial, deployment tutorial Date: Thu, 17 Dec 2015 14:01:37 +0100 Message-ID: <87y4cti5zi.fsf@gnu.org> References: <87zixjttsa.fsf@gmail.com> <20151209201329.20594c2e@weiserose.weiserose.de> <20151210045530.GA28215@thebird.nl> <87bn9uxy0l.fsf@gnu.org> <20151214062939.GA12226@thebird.nl> <87a8pdz9sk.fsf@gnu.org> <20151214092857.GA13044@thebird.nl> <20151214193654.GA22023@jasmine> <20151215101831.GA16741@thebird.nl> <87egeo7ze7.fsf@gnu.org> <20151216045304.GA19514@thebird.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55844) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a9YBm-0005bK-Lg for guix-devel@gnu.org; Thu, 17 Dec 2015 08:01:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a9YBh-0008EO-ML for guix-devel@gnu.org; Thu, 17 Dec 2015 08:01:46 -0500 In-Reply-To: <20151216045304.GA19514@thebird.nl> (Pjotr Prins's message of "Wed, 16 Dec 2015 05:53:04 +0100") 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Pjotr Prins Cc: guix-devel@gnu.org Pjotr Prins skribis: > In addition to the a packaging tutorial, I would also like a > deployment tutorial where explain how to do system configuration and > how to create a caching server/build server in a few steps. > > The information is there in the main docs (and source code), but what > we lack is a short descriptive list what steps one has to go through. When Florian (fps) was trying to build everything on his machine, we noticed that yeah, it=E2=80=99s easily done via a couple of Bash lines that= call out to =E2=80=98guix build=E2=80=99 and the likes, but we should really pro= vide a specific command for that, like =E2=80=98guix build --all=E2=80=99, at leas= t. People could set up Hydra, and we could provide GuixSD configurations that do that (we=E2=80=99ll have to anyway, for the new front-end server), = but that=E2=80=99s too much of a sledgehammer for use cases such as Florian=E2= =80=99s. > Ludo, I am happy to participate in this effort. I would like to > propose using org-mode on for the initial versions. Simply because I > am productive that way. I really think this kind of information should go in the canonical manual. =E2=80=9CDefining Packages=E2=80=9D and =E2=80=9CUsing the Configu= ration System=E2=80=9D were intended this way. I understand they are currently badly structured and incomplete, but I think we should fix them. Having a single canonical place for documentation is very important to me. This is too often dismissed in favor of chaotic documentation spread over several random places. For someone willing to contribute non-trivial documentation, I cannot imagine Texinfo being a significant barrier. For the most part, it=E2=80= =99s really trivial. WDYT? > Would that be OK? And, despite my own reservations on github's growing > role, I think at this stage github has the best functionality. Also > github invites contributions because many people are signed up. For > the short term, I suggest we use github for the tutorials. Github has > the right audience for readers too. Once it stabalizes it could go > into the main Guix tree. You can use GitHub for your own work if you want, of course. However, Guix itself will remain on Savannah, and its procedure will remain patches sent over email. I am fine with discussing improvements to our procedures, and I think it=E2=80=99s important to remain critical. However, promoting GitHub/GitLa= b, their proprietary software, and their inevitable attacks on user privacy is a no-go for me. Thanks, Ludo=E2=80=99.