all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix size reduction work group
Date: Fri, 7 Feb 2020 23:31:19 +0100	[thread overview]
Message-ID: <CAE4v=pgqft_mhbqSY1EkUSPvB-_o0N5xtf0hZLnNW2vNyCwMOQ@mail.gmail.com> (raw)
In-Reply-To: <87d0aq13op.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Hello Ludo,

Ludovic Courtès <ludo@gnu.org> ezt írta (időpont: 2020. febr. 7., Pén
22:36):

> Hi,
>
> 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.

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


> Ludo’.
>

Best regards,
g_bor

>

[-- Attachment #2: Type: text/html, Size: 2053 bytes --]

  reply	other threads:[~2020-02-07 22:31 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 [this message]
2020-02-08 13:40         ` zimoun
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

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

  git send-email \
    --in-reply-to='CAE4v=pgqft_mhbqSY1EkUSPvB-_o0N5xtf0hZLnNW2vNyCwMOQ@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.