From mboxrd@z Thu Jan  1 00:00:00 1970
From: zimoun <zimon.toutoune@gmail.com>
Subject: Re: Guix size reduction work group
Date: Sat, 8 Feb 2020 14:40:27 +0100
Message-ID: <CAJ3okZ3d7E14N-ZM8cH0TfmsQXxL9E3nX03bu4qeeuE5jvOT8A@mail.gmail.com>
References: <87pneul50i.fsf@ambrevar.xyz> <87blqdnjuv.fsf@gnu.org>
 <CAJ3okZ1s5-ak8jTcpzZxU5qj5JRuNJeGYJNVphA1_qOEFHEjyg@mail.gmail.com>
 <87d0aq13op.fsf@gnu.org>
 <CAE4v=pgqft_mhbqSY1EkUSPvB-_o0N5xtf0hZLnNW2vNyCwMOQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:46976)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <zimon.toutoune@gmail.com>) id 1j0QLi-0006x9-Ay
 for guix-devel@gnu.org; Sat, 08 Feb 2020 08:40:43 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <zimon.toutoune@gmail.com>) id 1j0QLh-0003nW-DW
 for guix-devel@gnu.org; Sat, 08 Feb 2020 08:40:42 -0500
In-Reply-To: <CAE4v=pgqft_mhbqSY1EkUSPvB-_o0N5xtf0hZLnNW2vNyCwMOQ@mail.gmail.com>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: =?UTF-8?Q?G=C3=A1bor_Boskovits?= <boskovits@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>

Hi,

On Fri, 7 Feb 2020 at 23:31, G=C3=A1bor Boskovits <boskovits@gmail.com> wro=
te:
> Ludovic Court=C3=A8s <ludo@gnu.org> ezt =C3=ADrta (id=C5=91pont: 2020. fe=
br. 7., P=C3=A9n 22:36):
>> zimoun <zimon.toutoune@gmail.com> skribis:

>> >> The thing is, I think it=E2=80=99s something that requires constant c=
are, every
>> >> time we add a package or modify an existing one.  It=E2=80=99s very e=
asy to lose
>> >> benefits that had been previously obtained through hard work!
>> >
>> > I have never thought, neither tried but is it possible to find and/or
>> > build all the packages that 'inherit' from a specific one?
>>
>> Nope (=E2=80=98inherit=E2=80=99 is purely syntactic, it doesn=E2=80=99t =
=E2=80=9Clive on=E2=80=9D at run time.)
>> What would it buy you, though?
>
> It is currently easy to break packages by updating a package that is inhe=
rited from. You have no way to know about that relationship by simple inspe=
ction, and is not discoverable by current tooling either. So I also believe=
 that it would be useful to at least be able to list them. One place where =
this becomes painful is in bootstrap chains.

Yes, exactly that. :-)


> Do you think this can be achieved somehow without complicating implementa=
tion?

Maybe grouping all the packages with the same 'origin'. It should
possible, isn't it?


Cheers,
simon