unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>,
	Josselin Poiret <dev@jpoiret.xyz>,
	 Mathieu Othacehe <othacehe@gnu.org>,
	Ricardo Wurmus <rekado@elephly.net>,
	 Simon Tournier <zimon.toutoune@gmail.com>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages
Date: Thu, 22 Jun 2023 13:25:47 -0400	[thread overview]
Message-ID: <CA+3U0ZkfNDO1QM3ztqBtGoV1SWvCFkJKdXu9+GWg4fAfo05Nig@mail.gmail.com> (raw)
In-Reply-To: <20230308120125.17560-1-ludo@gnu.org>

On Wed, Mar 8, 2023 at 7:03 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hello,
>
> This change makes things like:
>
>   guix build --with-input=guile=guile-next guix -n --no-grafts
>
> more useful and tractable.
>
> Low-level rewrites are still possible for packages not marked
> as hidden in 'commencement.scm', such as glibc:
>
>   guix build --with-latest=glibc hello -n
>
> Thoughts?
>
> Ludo'.
>
> Ludovic Courtès (2):
>   packages: Use SRFI-71 instead of SRFI-11.
>   packages: 'package-input-rewriting/spec' ignores hidden packages.
>
>  doc/guix.texi      | 21 ++++++++++++---------
>  guix/packages.scm  | 14 ++++++++------
>  tests/packages.scm | 20 +++++++++++++++++++-
>  3 files changed, 39 insertions(+), 16 deletions(-)
>
>
> base-commit: 0a37921d851b94aef6900214098dc5bd62b46e26
> --
> 2.39.1

(resending to guix-devel since the bug has been archived)

Ludo',

This has broken, for example, building clang with a newer version of
gcc using package-input-rewriting/spec. What do you think of adding a
hidden? property to enable the old behavior?

Alternatively, why are gcc, binutils, and libc used as build-time
dependencies rather than gcc-toolchain? gcc-toolchain could be
rewritten as a non-hidden package and use of the toolchain would
seemingly better support profiles created with
package->development-manifest.

Greg


       reply	other threads:[~2023-06-22 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230308120125.17560-1-ludo@gnu.org>
2023-06-22 17:25 ` Greg Hogan [this message]
2023-06-24 10:09   ` [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages Josselin Poiret
2023-09-14 15:41   ` 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=CA+3U0ZkfNDO1QM3ztqBtGoV1SWvCFkJKdXu9+GWg4fAfo05Nig@mail.gmail.com \
    --to=code@greghogan.com \
    --cc=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@gmail.com \
    /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).