public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: cal <cal@mail.meme.technology>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Remove rust completely
Date: Wed, 11 May 2022 19:02:50 -0700	[thread overview]
Message-ID: <84ae5b55-4552-168c-d217-f042640068e3@mail.meme.technology> (raw)
In-Reply-To: <CAFvvX=Y+zQYegVbAne=je85vGNX0a3QQ-P5tpuZTw=Lie1bkWA@mail.gmail.com>

On 5/11/22 18:41, Mansour Al Akeel wrote:
> Miles,
> Thank you for your response. The idea of "getting harder and harder"
> is hard to accept. Gentoo has always been about having choice> Firefox requires rust, but is there a way to disable this ?
> There must be another way to let the user decide if they need it or not !
At the distribution level, sure, but the Gentoo package maintainers
don't necessarily have the authority to control what upstream software
developers are doing.  I continue to find it perplexing how many people
on this list hold responsible the Gentoo packaging for the
decision-making of upstream developers.

Significant core components of Firefox are written in Rust, and have
been for years.  Whether or not this is a good thing is in the eyes of
the beholder, but it has nothing to do with the Gentoo packaging -- it's
a Mozilla decision.
> 
> And yes, the compile time is one of the factors in not wanting it on
> my system. The second factor is a natural reaction toward feeling that
> I am forced to have it.
> Another reason is the growing collection of compilers and development
> tools and their build time (gcc, bin-utils, llvm, clang ... etc.) and
> now rust.
> 
> Firefox itself takes a lot of time to build, and if rust is a must
> have, then maybe it is time for me to look into something else. I know
> there's firefox-bin, and if it doesn't need rust, then maybe it is an
> option.
> 
> On Wed, May 11, 2022 at 8:55 PM Miles Malone
> <m.malone@homicidalteddybear.net> wrote:
>>
>> If your *reason* for wanting to remove rust is the compile time, bear
>> in mind there is also a rust-bin package these days.  There are an
>> increasingly large number of major packages that have rust as a
>> dependency, so it's getting harder and harder to get away from.
>> Obviously anything from the mozilla foundation, but there's a lot of
>> others too.
>>
>> Miles
>>
>> On Thu, 12 May 2022 at 10:25, Julien Roy <julien@jroy.ca> wrote:
>>>
>>> You need to remove all packages that depend on virtual/rust
>>> To see which ones do, run `emerge -pv --depclean virtual/rust`
>>>
>>> Julien
>>>
>>>
>>>
>>> May 11, 2022, 20:22 by mansour.alakeel@gmail.com:
>>>
>>> I am trying to avoid installing rust and prevent emerge --update
>>> --deep world from installing it again.
>>> How to do this ?
>>>
>>>
>>



  reply	other threads:[~2022-05-12  2:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12  0:22 [gentoo-user] Remove rust completely Mansour Al Akeel
2022-05-12  0:25 ` Julien Roy
2022-05-12  0:55   ` Miles Malone
2022-05-12  1:41     ` Mansour Al Akeel
2022-05-12  2:02       ` cal [this message]
2022-05-12  2:24         ` Mansour Al Akeel
2022-05-12  3:19           ` Matt Connell
2022-05-12  2:05       ` [gentoo-user] " Grant Edwards
2022-05-12 16:21       ` [gentoo-user] " Wols Lists
2022-05-12  2:01   ` Mansour Al Akeel
2022-05-14 11:04 ` Michael Orlitzky

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=84ae5b55-4552-168c-d217-f042640068e3@mail.meme.technology \
    --to=cal@mail.meme.technology \
    --cc=gentoo-user@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