From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: Guix size reduction work group Date: Fri, 7 Feb 2020 23:31:19 +0100 Message-ID: References: <87pneul50i.fsf@ambrevar.xyz> <87blqdnjuv.fsf@gnu.org> <87d0aq13op.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000008f4bb0059e03f3ab" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53028) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j0CA2-0004uB-4i for guix-devel@gnu.org; Fri, 07 Feb 2020 17:31:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j0CA0-0001t0-Gj for guix-devel@gnu.org; Fri, 07 Feb 2020 17:31:42 -0500 In-Reply-To: <87d0aq13op.fsf@gnu.org> 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-mx.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: Guix Devel --0000000000008f4bb0059e03f3ab Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Ludo, Ludovic Court=C3=A8s ezt =C3=ADrta (id=C5=91pont: 2020. febr= . 7., P=C3=A9n 22:36): > Hi, > > zimoun skribis: > > >> The thing is, I think it=E2=80=99s something that requires constant ca= re, every > >> time we add a package or modify an existing one. It=E2=80=99s very ea= sy 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 inherited from. You have no way to know about that relationship by simple inspection, 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. Do you think this can be achieved somehow without complicating implementation? > Ludo=E2=80=99. > Best regards, g_bor > --0000000000008f4bb0059e03f3ab Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Ludo,

Ludovic Court=C3=A8s <ludo@gnu.org> ezt =C3=ADrta (id=C5=91pont: 2020. febr.= 7., P=C3=A9n 22:36):
Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

>> The thing is, I think it=E2=80=99s something that requires constan= t care, every
>> time we add a package or modify an existing one.=C2=A0 It=E2=80=99= s very easy 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<= br> > 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 upd= ating a package that is inherited from. You have no way to know about that = relationship by simple inspection, and is not discoverable by current tooli= ng 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.

Do you think this can be a= chieved somehow without complicating implementation?


Ludo=E2=80=99.

Best regards,
g_bor
--0000000000008f4bb0059e03f3ab--