unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix size reduction work group
Date: Sat, 8 Feb 2020 14:40:27 +0100	[thread overview]
Message-ID: <CAJ3okZ3d7E14N-ZM8cH0TfmsQXxL9E3nX03bu4qeeuE5jvOT8A@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=pgqft_mhbqSY1EkUSPvB-_o0N5xtf0hZLnNW2vNyCwMOQ@mail.gmail.com>

Hi,

On Fri, 7 Feb 2020 at 23:31, Gábor Boskovits <boskovits@gmail.com> wrote:
> Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2020. febr. 7., Pén 22:36):
>> zimoun <zimon.toutoune@gmail.com> skribis:

>> >> The thing is, I think it’s something that requires constant care, every
>> >> time we add a package or modify an existing one.  It’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
>> > build all the packages that 'inherit' from a specific one?
>>
>> Nope (‘inherit’ is purely syntactic, it doesn’t “live on” 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.

Yes, exactly that. :-)


> Do you think this can be achieved somehow without complicating implementation?

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


Cheers,
simon

  reply	other threads:[~2020-02-08 13:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:57 Guix size reduction work group Pierre Neidhardt
2020-02-04 16:22 ` zimoun
2020-02-04 17:59   ` Julien Lepiller
2020-02-05 15:18 ` Ludovic Courtès
2020-02-05 16:11   ` zimoun
2020-02-07 21:35     ` Ludovic Courtès
2020-02-07 22:31       ` Gábor Boskovits
2020-02-08 13:40         ` zimoun [this message]
2020-02-10 13:13       ` Tobias Geerinckx-Rice
2020-02-11 14:15         ` Ludovic Courtès
2020-02-08 16:43   ` Pierre Neidhardt
2020-02-09 23:45     ` zimoun
2020-02-10  8:09       ` Pierre Neidhardt
2020-02-10  8:46         ` Christopher Baines
2020-02-11 14:17           ` Ludovic Courtès
2020-02-10 10:30         ` zimoun
2020-02-10 12:33         ` Julien Lepiller
2020-02-11 14:20     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3okZ3d7E14N-ZM8cH0TfmsQXxL9E3nX03bu4qeeuE5jvOT8A@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).