From: Efraim Flashner <efraim@flashner.co.il>
To: Felix Lechner <felix.lechner@lease-up.com>,
Ian Eure <ian@retrospec.tv>,
guix-devel@gnu.org
Subject: Re: Rust-team branch status?
Date: Thu, 27 Jun 2024 16:47:53 +0300 [thread overview]
Message-ID: <Zn1tiYT1mduaCDzL@3900XT> (raw)
In-Reply-To: <Zn1kfDkwP8h9d9FX@ws>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
On Thu, Jun 27, 2024 at 03:09:16PM +0200, Tomas Volf wrote:
> Hello,
>
> On 2024-06-27 05:50:02 -0700, Felix Lechner via Development of GNU Guix and the GNU System distribution. wrote:
> > Hi Efraim,
> >
> > On Wed, Jun 26 2024, Efraim Flashner wrote:
> >
> > > The packages are public but hidden
> >
> > Interesting! How does that work, please? I looked at the package
> > definition [1] but could not see fields that hide it. Thanks!
>
> As far as I can tell *all* versions except the "official" are hidden. The
> "base" package (rust-1.55) has this property:
>
> (properties '((hidden? . #t)
> ...)
>
> All other rusts inherit from it, therefore getting the property as well. The
> "offical" rust package (currently at 1.55) has these properties:
>
> (properties (append
> (alist-delete 'hidden? (package-properties base-rust))
> (clang-compiler-cpu-architectures "15")))
>
> Making it install-able.
>
> At least I think this is how it works.
Yeah, that's how this one is hidden.
In the past the different rust packages used 'define' instead of
'define-public', but it turns out that with 'define-public' the CI
systems will recognize each package a separate package to be built, so
we can build up to the most recent rust piecemeal instead of from 1.54
straight to 1.75 in one evaluation.
The hidden? property is also how the gcc packages are hidden. 'guix
package -A ^gcc' doesn't show any straight gcc packages, only
gcc-toolchain ones, but adding alternate versions of gcc is the same as
adding any other package as an input.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-06-27 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 0:10 Rust-team branch status? Ian Eure
2024-06-21 13:18 ` Efraim Flashner
2024-06-21 13:46 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-25 15:48 ` Ian Eure
2024-06-26 7:46 ` Efraim Flashner
2024-06-26 14:09 ` Efraim Flashner
2024-06-26 17:21 ` Ian Eure
2024-06-27 12:50 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-27 13:09 ` Tomas Volf
2024-06-27 13:47 ` Efraim Flashner [this message]
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=Zn1tiYT1mduaCDzL@3900XT \
--to=efraim@flashner.co.il \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
/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).