From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: A few thing we might consider hosting Date: Sun, 3 Dec 2017 08:21:35 +0100 Message-ID: References: <20171202232926.GB23657@jasmine.lan> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113ecd3ab5622c055f6a73ed" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59730) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eLOao-0007DT-MA for guix-devel@gnu.org; Sun, 03 Dec 2017 02:21:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eLOan-0007ql-2K for guix-devel@gnu.org; Sun, 03 Dec 2017 02:21:38 -0500 Received: from mail-io0-x231.google.com ([2607:f8b0:4001:c06::231]:40048) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eLOam-0007qP-Iq for guix-devel@gnu.org; Sun, 03 Dec 2017 02:21:36 -0500 Received: by mail-io0-x231.google.com with SMTP id d21so15440648ioe.7 for ; Sat, 02 Dec 2017 23:21:36 -0800 (PST) In-Reply-To: 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: Leo Famulari Cc: Guix-devel --001a113ecd3ab5622c055f6a73ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I was aware of the discussion thread, however I could not find out what the current state is? Do we plan to modify this behaviour in the next release? The core-updates thing makes sense, thanks. 2017-12-03 8:19 GMT+01:00 G=C3=A1bor Boskovits : > Ok, thanks for clarification. > I > > 2017-12-03 0:29 GMT+01:00 Leo Famulari : > >> On Sat, Dec 02, 2017 at 05:28:51PM +0100, G=C3=A1bor Boskovits wrote: >> > Sometimes while working in guix I run into problems because: >> > 1. a tarball was removed or modified upstream >> > >> > It would be great to have the ability to install the latest release in >> all >> > the supported ways on all supported architectures, and have the abilit= y >> do >> > guix pull without problems. >> > Last time I tried that it did not worked, because one of the upstream >> > linux-libre tarballs was removed. It would be nice if we could afford = to >> > host the sources, so that at lesat a bare-bones guixsd suffered no suc= h >> > problems. >> >> We actually do host the sources, but Guix usually tries fetching them >> from upstream first, which can be annoying. We are discussing this here: >> >> >> >> > 2. some packages take very long time to build (notably guile) >> > >> > It would be nice, if we could provide the substitutes that the current >> > core-updates gnu-build-system needs. That would make development that >> needs >> > to be done on core-updates much more pleasant to those who are working >> in a >> > restricted hardware environment. >> >> We use the core-updates branch like this: >> >> 1) For a couple months we just push changes to core packages to the >> branch without worrying about if it works or not. >> 2) After some time, we try building the branch and fix everything that >> is broken. Once that is done, we merge it into the master branch, which >> is what `guix pull` uses by default. >> >> So, for most of the life of a core-updates branch, it's likely that no >> packages will be buildable, and thus we don't even try, so there are no >> substitutes. >> >> Once we start building it, substitutes are available in the normal way. >> > > --001a113ecd3ab5622c055f6a73ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was aware of the discussion thread, however I could not = find out what the current state is? Do we plan to modify this behaviour in = the next release?

The core-updates thing makes sense, th= anks.

= 2017-12-03 8:19 GMT+01:00 G=C3=A1bor Boskovits <boskovits@gmail.com&= gt;:
Ok, thanks f= or clarification.
I
=

2017-12-03 0:29 G= MT+01:00 Leo Famulari <leo@famulari.name>:
On Sat, Dec 02, 2017 at 05:28:51PM +0100, G=C3=A1bor= Boskovits wrote:
> Sometimes while working in guix I run into problems because:
> 1. a tarball was removed or modified upstream
>
> It would be great to have the ability to install the latest release in= all
> the supported ways on all supported architectures, and have the abilit= y do
> guix pull without problems.
> Last time I tried that it did not worked, because one of the upstream<= br> > linux-libre tarballs was removed. It would be nice if we could afford = to
> host the sources, so that at lesat a bare-bones guixsd suffered no suc= h
> problems.

We actually do host the sources, but Guix usually tries fetching the= m
from upstream first, which can be annoying. We are discussing this here:
<https://bugs.gnu.org/28659>

> 2. some packages take very long time to build (notably guile)
>
> It would be nice, if we could provide the substitutes that the current=
> core-updates gnu-build-system needs. That would make development that = needs
> to be done on core-updates much more pleasant to those who are working= in a
> restricted hardware environment.

We use the core-updates branch like this:

1) For a couple months we just push changes to core packages to the
branch without worrying about if it works or not.
2) After some time, we try building the branch and fix everything that
is broken. Once that is done, we merge it into the master branch, which
is what `guix pull` uses by default.

So, for most of the life of a core-updates branch, it's likely that no<= br> packages will be buildable, and thus we don't even try, so there are no=
substitutes.

Once we start building it, substitutes are available in the normal way.


--001a113ecd3ab5622c055f6a73ed--