From: Christopher Baines <mail@cbaines.net>
To: 40876@debbugs.gnu.org, mbakke@fastmail.com
Subject: [bug#40876] [PATCH core-updates] gnu: libgc/static-libs: Mark it as hidden.
Date: Sun, 26 Apr 2020 20:14:59 +0100 [thread overview]
Message-ID: <87zhaym53g.fsf@cbaines.net> (raw)
In-Reply-To: <20200426185823.5652-1-mail@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> * gnu/packages/bdw-gc.scm (libgc/static-libs)[properties] Set hidden? to #t.
> ---
> gnu/packages/bdw-gc.scm | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/bdw-gc.scm b/gnu/packages/bdw-gc.scm
> index 112a161f94..50e4951dc1 100644
> --- a/gnu/packages/bdw-gc.scm
> +++ b/gnu/packages/bdw-gc.scm
> @@ -91,7 +91,8 @@ C or C++ programs, though that is not its primary goal.")
> libgc
> (arguments (substitute-keyword-arguments (package-arguments libgc)
> ((#:configure-flags flags ''())
> - `(cons "--enable-static" ,flags))))))
> + `(cons "--enable-static" ,flags))))
> + (properties '((hidden? . #t)))))
>
> (define-public libgc-7
> (package
Forgot to include you Marius when I sent this patch. Does this seem
sensible?
Otherwise you get this libgc variant when you use Guix on the command
line, and commands like guix lint complain.
./pre-inst-env guix lint libgc
guix lint: warning: ambiguous package specification `libgc'
guix lint: warning: choosing libgc@8.0.4 from gnu/packages/bdw-gc.scm:90:2
I hope that setting the properties doesn't involve rebuilding anything.
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2020-04-26 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 18:58 [bug#40876] [PATCH core-updates] gnu: libgc/static-libs: Mark it as hidden Christopher Baines
2020-04-26 19:14 ` Christopher Baines [this message]
2020-04-28 14:39 ` Marius Bakke
2020-04-28 21:56 ` bug#40876: " Christopher Baines
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=87zhaym53g.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=40876@debbugs.gnu.org \
--cc=mbakke@fastmail.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 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.