all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46650@debbugs.gnu.org, Carl Dong <contact@carldong.me>
Subject: bug#46650: Extending package transformation options
Date: Fri, 26 Feb 2021 22:44:01 +0100	[thread overview]
Message-ID: <86czwm1p3y.fsf@gmail.com> (raw)
In-Reply-To: <87h7m12xfw.fsf@gnu.org>

Hi,

On Wed, 24 Feb 2021 at 18:21, Ludovic Courtès <ludo@gnu.org> wrote:

>> So here, a transformation could be applied.  For example, build all
>> the dependencies without testing them;  at the 'define gnutls' (&co)
>> step or in the map.  Why not?
>
> Sure, but how do you get a user-specified transformation to this line?

I do not know (yet?). :-)

First, we are only speaking about “guix time-machine” and second, only
about corner cases which could break in the future, as expiration.
Right?
We are not talking about general transformations applied to self (even
if it could be great).

So we could imagine something like ’set-build-from-command-line’ or
’set-build-option’ to tweak self only for the inferior.  I have not
traced (yet) on the stack of calls from “guix time-machine” to self via
the inferiors, but somehow it looks like passing arguments.

Well, be able to tweak how to build Guix via the time-machine appears to
me better than configuring a build machine ahead of time.  It is like
predicting the future and instead we should try to have a flexible
present in order to fix the past once in the unpredictable future. :-)


Cheers,
simon




      reply	other threads:[~2021-02-26 21:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 23:24 bug#46650: Extending package transformation options Carl Dong
2021-02-20  0:17 ` Leo Famulari
2021-02-20 14:00   ` Ludovic Courtès
2021-02-20 13:57 ` Ludovic Courtès
2021-02-23 22:22   ` zimoun
2021-02-24 11:11     ` Ludovic Courtès
2021-02-24 13:43       ` zimoun
2021-02-24 17:21         ` Ludovic Courtès
2021-02-26 21:44           ` zimoun [this message]

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=86czwm1p3y.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=46650@debbugs.gnu.org \
    --cc=contact@carldong.me \
    --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.