[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59278: how gcc-toolchain can depends a package who doesn't exists?
From: |
bbb ee |
Subject: |
bug#59278: how gcc-toolchain can depends a package who doesn't exists? |
Date: |
Tue, 15 Nov 2022 23:04:36 +0100 |
In the documentation, when it says "guix search" search matching package, if users don't find a package defined in .scm (hidden or no), users can consider it is a bug, because that doesn't match the behavior described in the specification (here, the manual and "guix search --help").
Hi,
On Tue, 15 Nov 2022 at 00:53, bbb ee <blasforr@gmail.com> wrote:
> in commit c81457, how gcc-toolchain can depends a package who doesn't
> exists?
The package exists, it is ’hidden’ – it means not accessible at the CLI
level. The ’inherit’ copies, so gcc-11 is also hidden, for instance.
--8<---------------cut here---------------start------------->8---
(define-public gcc-4.7
[...]
(hidden-package
(package
(name "gcc")
(version "4.7.4")
(define-public gcc-4.8
(package (inherit gcc-4.7)
(version "4.8.5")
[...]
(define-public gcc-11
(package
(inherit gcc-8)
(version "11.3.0")
--8<---------------cut here---------------end--------------->8---
The package ’gcc’ by itself is not barely useful because you also need
linker etc. Well, you usually need a complete toolchain, named
gcc-toolchain. ;-)
See manual: <https://guix.gnu.org/manual/devel/en/guix.html#The-GCC-toolchain>
So this is not a bug and I miss how what could be improved. Closing?
Cheers,
simon