unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Jeffrey Walton <noloader@gmail.com>, 43303@debbugs.gnu.org
Subject: bug#43303: GCC package name
Date: Thu, 10 Sep 2020 13:16:36 +0200	[thread overview]
Message-ID: <CAJ3okZ3o2XJuOsL+ohgkf9UQtdTXPxA19b0rRM4=tB4zOygQUg@mail.gmail.com> (raw)
In-Reply-To: <87a6xxhqfq.fsf@gnu.org>

Hi Ludo,

On Thu, 10 Sep 2020 at 12:41, Ludovic Courtès <ludo@gnu.org> wrote:

> > With the aliases in place, a command like 'guix install gcc' works as expected.
>
> I’ve now added such an alias:
>
>   https://git.savannah.gnu.org/cgit/guix.git/commit/?id=f17e1802ec325e5cc86d4908f05ac69aafdf39da

Nice use of deprecated-package. :-)

About discoverability (guix search gcc) there is still 2 issues:

 1. libgccjit inherits from gcc-9 but the synopsis/description is not updated.
 2. gccgo uses custom-gcc and so reuse the same synopsis/description.

The #1 is easy to fix -- I can send a patch which precises the
synopsis/description of libgccjit.

What is the best for #2?  Add 2 optional arguments to 'custom-gcc'
(synopsis and description)?  Other?


Last, it is unfortunate that the package gccmakedep has the exact same
number of occurence of the term 'gcc' but it is not an issue.

Cheers,
simon




  reply	other threads:[~2020-09-10 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  5:20 bug#43303: GCC package name Jeffrey Walton
2020-09-10  6:18 ` Malte Gerdes
2020-09-10  8:34 ` zimoun
2020-09-10 10:33 ` Ludovic Courtès
2020-09-10 11:16   ` zimoun [this message]
2020-09-10 11:32     ` Ricardo Wurmus
2020-09-10 11:43       ` zimoun
2020-09-10 13:22         ` Ricardo Wurmus
2020-09-11 16:11     ` zimoun
2020-09-10 11:22   ` Jeffrey Walton

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='CAJ3okZ3o2XJuOsL+ohgkf9UQtdTXPxA19b0rRM4=tB4zOygQUg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=43303@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=noloader@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).