public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] making rust-bin ordered first in virtual/rust
Date: Tue, 18 Jan 2022 17:13:39 +0000	[thread overview]
Message-ID: <874C5E64-BF0B-4FBD-B09A-D59BFF96FC18@gentoo.org> (raw)
In-Reply-To: <ffaa5fabecc42c1a5e06003741c2bf7afc65ac1f.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]



> On 17 Jan 2022, at 23:24, Georgy Yakovlev <gyakovlev@gentoo.org> wrote:
> 
> Hi,
> 
> I've been approached multiple times with that request, and a lot of
> time I see new users completely destroyed by rust build time and disk
> space requirements.
> 

I'll out myself as being one of these people!

> WDYT about switching order of rusts in a virtual?
> 
> RDEPEND="|| (
>        ~dev-lang/rust-${PV}
>        ~dev-lang/rust-bin-${PV}
> )"
> 
> 
> becomes
> 
> RDEPEND="|| (
>        ~dev-lang/rust-bin-${PV}
> 	~dev-lang/rust-${PV}
> )"
> 
> 
> Existing installs should be unaffected ofc.
> But portage may prefer to depclean rust and not rust-bin if both are
> present.
> Users who wish to use source version at all times can just add it to
> world file.
> 
> I see both positives and negatives of doing that, but would like to
> reach out to community first.

I'd like to do -bin first to be consistent with OpenJDK, IcedTea,
and to improve first-install experience.

Not that I'm advocating for removing source builds or anything
like that, but I dare say Rust is generally not something that people
can customise much anyway.

As Ionen has noted, we did already switch in desktop stages.

Best,
sam


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  parent reply	other threads:[~2022-01-18 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 23:24 [gentoo-dev] [RFC] making rust-bin ordered first in virtual/rust Georgy Yakovlev
2022-01-17 23:56 ` Dale
2022-01-18  2:58 ` Ionen Wolkens
2022-01-18  4:38   ` Georgy Yakovlev
2022-01-18  6:30   ` Joonas Niilola
2022-01-18  7:48   ` Jaco Kroon
2022-01-18 17:13 ` Sam James [this message]
2022-01-18 17:53   ` Toralf Förster
2022-01-20 21:10 ` Piotr Karbowski
2022-01-20 21:19   ` Toralf Förster
2022-01-20 21:32   ` Rich Freeman
2022-01-21 16:52     ` Joshua Kinard
2022-01-20 21:32 ` Brian Evans
2022-01-21  1:01   ` Michael Orlitzky
2022-01-21  6:20   ` Joonas Niilola
2022-01-21  9:22   ` Mart Raudsepp
2022-01-21 10:29     ` Peter Böhm
2022-01-21 10:34       ` Fabian Groffen
2022-01-21 16:08 ` Alec Warner

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=874C5E64-BF0B-4FBD-B09A-D59BFF96FC18@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox