[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43303: GCC package name
From: |
zimoun |
Subject: |
bug#43303: GCC package name |
Date: |
Thu, 10 Sep 2020 13:43:21 +0200 |
Hi Ricardo,
On Thu, 10 Sep 2020 at 13:31, Ricardo Wurmus <rekado@elephly.net> wrote:
> > What is the best for #2? Add 2 optional arguments to 'custom-gcc'
> > (synopsis and description)? Other?
>
> custom-gcc returns a package value, so we can inherit from that and
> overwrite the synopsis and description fields.
Well, custom-gcc is already an inherit. So it seems awkward to inherit twice.
But yes, since it is the only case, it could be the simplest:
gccgo-4.9 would become only 'define' and a new 'gccgo' would be
inherit from gccgo-4.9 and would be define-public.
Cheers,
simon