Georgy Yakovlev 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.

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.

Thanks!

--
Georgy

As a user, if I recall correctly, if a user wants rust-bin, all they
have to do is emerge -1 rust-bin and then let whatever package pull in
the virtual for rust.  The virtual will be satisfied and rust-bin will
be used.  From my understanding, that is the purpose of virtuals,
allowing users to pick what they want to use to satisfy the
requirement.  I wouldn't want either rust in my world file as it is not
a package I use directly.  It should be a dependency of another package,
such as Firefox. To me, this sounds like there should be a note added to
a install guide so new users are aware of this, provided it isn't
already mentioned. 

Gentoo is known for compiling from sources.  Defaulting to a package
that is a binary but available as a package from source that requires compiling, that would be unexpected. 

Just my $0.02 worth, as a user. 

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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.

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.

Thanks!

--
Georgy

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Jan 17, 2022 at 03:24:23PM -0800, Georgy Yakovlev 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.

fwiw it may be a bit mitigated by the new desktop stages that come with
rust, or at least it won't be the first thing they see when they try
to build their brand new desktop install until a rust update.

It's nice if users can get a basic desktop before worrying about how to
handle rust. Not that desktop stages are heavily visible/known so new
users may not always pick them.

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.

Haven't tested how it reacts, but wouldn't that be an issue with system-bootstrap in situations where it pulls rust-bin to build itself?

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.

Unsure what I like best, I generally agree should default to sources
but I do see new users complaining about building rust every few days.
Not that the step of telling them that rust-bin exists is that bad
(part of the issue is that they don't know it's an option).

--
ionen

-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmHmLO0ACgkQskQGsLCs QzRicAf+P7ADPxVnIwRroV9GM56NS2jovkK12m16+r6nY3DUuGWZbrSBBBUo8bpr QpWI7L65Foyte8KtmDRB0pHwHBe8MSVXpCfaEZ3Yy5Y4uRznKrPgfoKYYKfRGSDF hlpfbhtCYxxwyT/4Nli7xEV1Vi9ZbSeu5g8HwFOSz2oC+2m/N11b2TSZY513YtTu 2Wd8SvBV3r1SebPJ/d+D7QheVTM6hrpqUzx8NF2odicVPVVRrHIKPREboMnuLNW0 zcrjNI8kbhvmLzUNfRW4OPke9sBp+bJVWpwdroWnQfItaDiKaJxhR47SDoFhdF7B +d8nFkOl+ankWw5eodjPrwvnBRbCmQ==
=C2MX
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 2022-01-17 at 21:58 -0500, Ionen Wolkens wrote:

On Mon, Jan 17, 2022 at 03:24:23PM -0800, Georgy Yakovlev 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.

fwiw it may be a bit mitigated by the new desktop stages that come
with
rust, or at least it won't be the first thing they see when they try
to build their brand new desktop install until a rust update.

It's nice if users can get a basic desktop before worrying about how
to
handle rust. Not that desktop stages are heavily visible/known so new
users may not always pick them.

indeed it helps, but it takes time for users to discover/consider this.
it mostly hits very new users or users of containers/vms, who don't
have enough disk space or ram.

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.

Haven't tested how it reacts, but wouldn't that be an issue with system-bootstrap in situations where it pulls rust-bin to build
itself?

it can build itself with non-bin too. as long as it's same or ver-
minus-1 and is installed, if not installed it will pull rust-bin of
matching version.
also system-bootstrap is stable-masked (for various reasons), so I'm
not too worried about it. ~kw users know their way around.

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.

Unsure what I like best, I generally agree should default to sources
but I do see new users complaining about building rust every few
days.
Not that the step of telling them that rust-bin exists is that bad
(part of the issue is that they don't know it's an option).

If I had clear answer myself I would not be asking opinions here =)
just trying to understand if I'm missing something or my view is too
different.
developer and user opinions all are helpful to build picture.
I receive at least weekly complaint about how resource-intensive rust
build is, that counts too.

for now on stable systems, if user types, let's say,
$ emerge ripgrep

with USE=-system-bootsrap (the default):
portage will pull virtual/rust, which will pull dev-lang/rust, which
will bootstrap itself by downloading proper rust-bin tarball, but not
as a package, just as a tarball behind the scenes.

with USE=system-bootstrap:
portage will pull virtual/rust, which will pull dev-lang/rust-bin, and
build dev-lang/rust, to build ripgrep.

USE=system-llvm (also stable-masked) complicates picture even more.

We've had openjdk-bin and icedtea-bin as default provider for as long
as I can remember, before I started to maintain it. works fine.

PS:
and just to be clear - I'm not pushing for it, just asking for input.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------KsMPF1RpYsPiBM9hSAFYjSEc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 18.1.2022 4.58, Ionen Wolkens wrote:

Unsure what I like best, I generally agree should default to sources
but I do see new users complaining about building rust every few days.
Not that the step of telling them that rust-bin exists is that bad
(part of the issue is that they don't know it's an option).

Indeed, can see both ways. On my desktop I use rust, and on my laptop+containers rust-bin. Having to package.mask rust so rust-bin gets
pulled might not be the first thing new users are aware.

To make things more complicated...
IUSE="+binary"
RDEPEND="binary? ( ~dev-lang/rust-bin-${PV} )
!binary? ( ~dev-lang/rust-${PV} )"

or "+pre-compiled" or something ;)

-- juippis

--------------KsMPF1RpYsPiBM9hSAFYjSEc--

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEltRJ9L6XRmDQCngHc4OUK43AaWIFAmHmXplfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk2 RDQ0OUY0QkU5NzQ2NjBEMDBBNzgwNzczODM5NDJCOERDMDY5NjIACgkQc4OUK43A aWIPrgf/SpAM3gYWbQJ+x0WI/UJs/L2QCHnb5MupKdIG6M/SoYAb3RNyHfEDWun/ JJfDKbXQjtH432Yabh/pUeDUiIgdMBJsS4IO2Wjbd5lfqOwj6xXoxdZtTF7ta1Ay fAd0TSqvO4AhVuyo+eA64b6uORRDWWVyUMmPVVFEJlf0Hf1WX6jL9k3oKnj7MZgP DeOUSTIqNOcOfMiBMGmuXF8Wr4fZonIJDNbiOA2t9ibswDjPY8j74STe5Q/xomUL mEa+MZ5Ap4t10mmqiC8XXiiymA5G6u4nbEwTpg16SBp9rcTdN7EhHwt0q5yoOx4p F9seCjiZDQdeKMD2gCJjp4XNPGRSpg==
=2gg1
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On 2022/01/18 04:58, Ionen Wolkens wrote:

Unsure what I like best, I generally agree should default to sources
but I do see new users complaining about building rust every few days.
Not that the step of telling them that rust-bin exists is that bad
(part of the issue is that they don't know it's an option).

Perhaps output a notice in rust's pkg_setup() that you're using the
source version and that it takes a long time to build, and consumes lots
of resources and you may want to consider rust-bin?  Possibly with some variable in make.conf or some USE to turn that off?

Kind Regards,
Jaco

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------Tn1OPrgWwafgOkF9RHlrhTEk
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

T24gMS8xOC8yMiAxODoxMywgU2FtIEphbWVzIHdyb3RlOg0KPiBOb3QgdGhhdCBJJ20gYWR2 b2NhdGluZyBmb3IgcmVtb3Zpbmcgc291cmNlIGJ1aWxkcyBvciBhbnl0aGluZw0KPiBsaWtl IHRoYXQsDQpJJ20gbm90ID8gOykNCg0KLS0gDQpUb3JhbGYNClBHUCAyMzIxN0RBNyA5Qjg4 OEY0NQ0K

--------------Tn1OPrgWwafgOkF9RHlrhTEk--

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEE4Aq096H1MGPqWQN3byNRLEwPvR0FAmHm/pkFAwAAAAAACgkQbyNRLEwPvR1X 7g/9HsX4H3Eel14m2Fd9iH5ktb73Zeb8pQCQ5IAYaz2TGFqQtQU3MXP3K/tTcYUfFqK8ShFJnrg9 XYlzKwlXm2JORUyVYtlTdxt2NLnkEBgSivgoFjBK0cx03RU1hr7wZVpPj6wkdWbRS8fCcuDIiJVH oEp1uXwBPa1WlJV6uE1renVXZbEXV20KDp+u4YL9t/IO8tPFKE+JxkpMmu6xDSIHbqc50mapH+Yn fC2M1dhg+H+9h/UnmS/AssPML9b8ZK7N6C0LzUXNxdM7z49gvRtbhHvV/pZff2yvBTEvJpLR8UQL 9ygoL/hxtwT0xU+1ag6rO1umV7LOgsi1vZXRniZP+FxUE2xtZHXzOGYHNP8lLOblE2OIyr8t1W4R rBVswNzO7jBkiNMFASbIk3ABqohWY8You7//ZAgQaTt3rO7Di3Cp2P/TJa8mtBQDvhnbKHUq41pF Qz22W30dJZrx8BvBCr83vD8rAWpi3V/z0hK7wSJK2Kr2t1LV5GxhiCIeiuNGSAFtr9FgoK4sf/0T L+jCJgnMLFvqNeEXn0c9UvoyxO5/QzMV85uKi87I5MFzz4w8daX1/xmwvhOXOmAR5sbF8DlOJd2t QJYWhxIl/3MAD1MFA7/DGrJxZYfu38AQiXuAnmjJ2i5zpMjZrdVb2zUViD0RFA8Vi+Xc0dVr4+9V j3Y=
=aDGs
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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


-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEYOpPv/uDUzOcqtTy9JIoEO6gSDsFAmHm9UNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYw RUE0RkJGRkI4MzUzMzM5Q0FBRDRGMkY0OTIyODEwRUVBMDQ4M0IACgkQ9JIoEO6g SDt+dggAr4QpKMEbaps99cMh1Czqf9+3jQ6Ytk28C8w3dFbXAkRw8RGUJmw5Ml/L TK6H5i96ajdldEoSxqym8bI2GaP48wztO9pl0HSvfY/S86IbpCecP1zpA+KAEm4q lAcXFJVxpePJPifqbkyFBBjn37pmFgYhm+cyap7o4wSusYvnZkABu3eiXuy/cDR6 uAV1asS5Q/NmyW2jY/BOM5R55mbSwWJlWjy+lA+JXFyt0kUOQhEBaZ5D14YjgU0O yS85UaNxuPBlvgOeTCmI07m3lpFq3t2izKVFQ6LniE9MXVOy1Y2UH5JrX6CPkTR6 l5mJMgvzukbrurHU1NzF+vv4DJ5IRA==
=GDjT
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 18/01/2022 00.24, Georgy Yakovlev 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.

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 would prefer to have source based one first.

Ideally we'd have some way to mark binary packages with new EAPI and
have FEATURES flag like 'prefer-binary' and go with -bin in case there's
|| ( ) dependencies list, regardless of the original order in virtual.
This way everyone could be happy and not choose one workflow over another.

-- Piotr.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------nOyI9Iyn1WRWUSH0w2ARxLj0
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

T24gMS8yMC8yMiAyMjoxMCwgUGlvdHIgS2FyYm93c2tpIHdyb3RlOg0KPiBJIGFuZCBoYXZl IEZFQVRVUkVTIGZsYWcgbGlrZSAncHJlZmVyLWJpbmFyeScgYW5kIGdvIHdpdGggLWJpbiBp biBjYXNlIA0KPiB0aGVyZSdzIHx8ICggKSBkZXBlbmRlbmNpZXMgbGlzdCwgcmVnYXJkbGVz cyBvZiB0aGUgb3JpZ2luYWwgb3JkZXIgaW4gDQo+IHZpcnR1YWwuDQorMQ0KDQotLSANClRv cmFsZg0KUEdQIDIzMjE3REE3IDlCODg4RjQ1DQo=

--------------nOyI9Iyn1WRWUSH0w2ARxLj0--

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEE4Aq096H1MGPqWQN3byNRLEwPvR0FAmHp0d4FAwAAAAAACgkQbyNRLEwPvR0J QQ/9Gw9AoJxFj9WiNiCT2424RVN3EJslNscgikuUkJc1vOkDtWAaQdvVtxyv5RJaO2x4dPXLEyDH KrzZV/6ZbASNg4ULjTihhljcBiLrfS8yWlPLBmWLG2CyYWo9RjaQGaSCFxWOhwabMncLLUs92Vqr SlGiQpe7we5Uojz3MWMMU0SPKo5r/6DM6IuEPTaCSa7oLcAMFPCr9lrrs+D7aGC5GR0KLxCgP4NT t5uGWIHiwSG+sMYeziDCQl5DD/6GV/vLO05wE63HHndDpEjt4AxeJVKc1ZX3CyC2fIUJ0iDo7GE2 pGJjmmVAgHg36izRgii/+3IO5PpjEr3RL3nT0Xe43QpQtV6DJ1WaD9uHID8GbIddi6BAhfDjfIyZ ndslT/Uy5nba+C5uJNDpk8Kaq/W4AHw4ExfOqhOIPglgp+4lm8jPIamorHitJR6SwLlV971q9H6b RF/SfmJjzzNamraWQrJf9rwGBwbmS29MvmO80njZjArAieqsXxfko3E/61qATKt5mY68DzvoimeB pGD20Le1mr9HOpqDMUdT6725JAafR7+2yP3HF4boSsyzOD3ePwCOujUZiLYTlFXoQ4YfGQbfh4DA MRZRzMSeWb86VpD/aQeSY0rhrapv2A3pMVyJuQxOkSJPpVV9A+GdAjMDHbeRH4uvW5vgXUJdxsmF eb8=
=LCTA
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, Jan 20, 2022 at 4:10 PM Piotr Karbowski <slashbeast@gentoo.org> wrote:

Ideally we'd have some way to mark binary packages with new EAPI and
have FEATURES flag like 'prefer-binary' and go with -bin in case there's
|| ( ) dependencies list, regardless of the original order in virtual.
This way everyone could be happy and not choose one workflow over another.

Ideally we'd just have a repository of binary builds for everything
with default USE flags for a few profiles, and users could choose to
configure portage to just download the binary package if the flags
match, and of course this could be overridden per-package. Then there
would be no need for -bin anything. We have to maintain half of that
for the stage builds anyway.

I don't have a strong preference but I doubt that many of our users
receive any benefit whatsoever from building rust from source, and so
I'd suggest -bin ought to be the default. However, having a
pre-installation notice that the -bin is available with a link/etc to
how to use it seems reasonable. I bet a lot of users spend more time
getting the source build to work than it would take to just
reconfigure things so that they get the -bin. If users are building
in a tmpfs or with numerous parallel jobs odds are that they'll end up
with a build failure for rust - CPU cores are way cheaper than RAM.

--
Rich

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------1CqSt3gMvyyQmZTdeZK4xDhk
Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

T24gMS8xNy8yMDIyIDY6MjQgUE0sIEdlb3JneSBZYWtvdmxldiB3cm90ZToNCj4gSGksDQo+ IA0KPiBJJ3ZlIGJlZW4gYXBwcm9hY2hlZCBtdWx0aXBsZSB0aW1lcyB3aXRoIHRoYXQgcmVx dWVzdCwgYW5kIGEgbG90IG9mDQo+IHRpbWUgSSBzZWUgbmV3IHVzZXJzIGNvbXBsZXRlbHkg ZGVzdHJveWVkIGJ5IHJ1c3QgYnVpbGQgdGltZSBhbmQgZGlzaw0KPiBzcGFjZSByZXF1aXJl bWVudHMuDQo+IA0KDQpJIGJldCB0aGF0IHRoZSBwZW5kaW5nIHBvbGtpdCBtZXJnZSByZXF1 ZXN0WzFdICh3aGljaCBpcyBqdXN0IGFib3V0IA0KcmVhZHkgYW5kIGJsZXNzZWQgYnV0IG5v dCBtZXJnZWQgYnkgZGV2cykgd291bGQgc2VyaW91c2x5IGRyb3AgbWFueSANCnBlb3BsZSdz IGNvbmNlcm5zIG92ZXIgcnVzdC4NCg0KVXNpbmcgZHVrdGFwZSBvbiBtb3N0IHN5c3RlbXMg d2lsbCBzdWZmaWNlIGZvciBwb2xraXQgb25jZSBpbmNsdWRlZC4NCg0KR05PTUUgYW5kIE1v emlsbGEgcHJvZHVjdHMgc3RpbGwgcHVsbCBpbiBzcGlkZXJtb25rZXkgYnV0IG90aGVyIHVz ZXJzIA0Kd2lsbCBoYXZlIGEgbXVjaCByZWR1Y2VkIHJlcXVpcmVtZW50IGZvciBydXN0Lg0K DQpCcmlhbg0KDQpbMV0gaHR0cHM6Ly9naXRsYWIuZnJlZWRlc2t0b3Aub3JnL3BvbGtpdC9w b2xraXQvLS9tZXJnZV9yZXF1ZXN0cy85Nw0KDQo=

--------------1CqSt3gMvyyQmZTdeZK4xDhk--

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEZsLkTtkOMnWOfVXA0feB7/n0o7YFAmHp1O4FAwAAAAAACgkQ0feB7/n0o7YS QhAAyb1J4tep5j+dvbzom0N7CTWpzPKKPascVxPxKZZMKx8SHv82aMZYiyRyOyJedH5DxylQn5cn grPfSEGAe2n1hUZgeXZW7Rwv1SUtsGL41YBH6LDNsvrUu6sSD8E0nJhTJyCRCabH+ff0A26z+smP KE3uBPPXDslLBpWJN0NKDJsdk67iuPHXBMJKc3hc5Gu+n/+qpWtzmBEelr260ZTY1tbqIiHAwdYS 4Wdiz4p+P7SZ1OpLoeuCTokG3GfHh1XjVs+sHCz3tw08oYNnChg1tS5AB2hgiFTmFVDBcl51ymBt USYzpMbovf+395b5XBa2DcxfmuXK6DbVZiXjU66jkeei+IQp1V+pfzqEU+Xfscr2AStC9Ugafc/8 UAJITD26svtzLVKktXpu6A/uW9wE3iyu9V5M7y1Li+58nrZaHgeRwRXThS1NFNulLrsi/xH7x5kZ SqtFolsBPYMuTBpL2ECPBzIN30E5Cp15K91y8+va4Nigco2coqCOLeavdsEr/zvg+BrXxbQSbOys COx8L8Diijl2E5EW5MMgWSETUqpkanEK0Q6sXwio1C+gIa+N1wW9s2S9xwNLMEWwMf9+rFZgzv70 fr49IYntSIsWbYD+p9ncdWVkl5e+ZIlzNo6LWadeJ68oXXkXlRsgxlc8OrKEUYbQg90qkoSby2Zq aSA=
=dw/C
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022-01-20 16:32:30, Brian Evans wrote:

GNOME and Mozilla products still pull in spidermonkey but other users
will have a much reduced requirement for rust.

Avoiding librsvg used to be difficult because it's required by our GTK
icon packages to render PNGs from SVGs. Luckily dilfridge's binrepo
now makes it easy to download pre-rendered icons, and there's no security/performance/legal concerns with pre-rendered PNGs, so using
them shouldn't present any moral dilemmata. You mainly just have to
replace Firefox, Thunderbird, and GIMP.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------npJ2KW0vqwJNPP7svu2VgeU9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 20.1.2022 23.32, Brian Evans wrote:

GNOME and Mozilla products still pull in spidermonkey but other users
will have a much reduced requirement for rust.

While Firefox and Thunderbird contain a js engine, no mozilla product
depends externally on spidermonkey. I was wondering recently why mozilla project maintains it and not Gnome or Freedesktop, but I guess it's
because of the similarities shared by the ebuilds between firefox,
thunderbird and spidermonkey.

-- juippis

--------------npJ2KW0vqwJNPP7svu2VgeU9--

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEEltRJ9L6XRmDQCngHc4OUK43AaWIFAmHqUJZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk2 RDQ0OUY0QkU5NzQ2NjBEMDBBNzgwNzczODM5NDJCOERDMDY5NjIACgkQc4OUK43A aWJpoQf+OEFdgT8eFQNyZWa0kcVoe8HGNnWlAsy2AQ3gcM538S/3YyUjVEA91U7x H7wlCNRQhlxG/XHBMkWInmHqoie1AYwOMe1UTffS3yFQ+00GPBEWa1utgVq1kj5U hlS74n8eGlyz9oKMYEUrHpFYk4MKa5gyNcYhpOzjMysZDRF8QYRl8q+IJ+L2vTtI 0mi5aZKZ+cPipfeVBbIT1bMXt0Ae4uN1PJSqEq/L4q7EUggvJJCQ3vZk/ALlH6N3 WWJKrMVbj0AVtLNFhQh2cwbbH4OCkM3TcXSOk0iy+myTWO5Su31X9AN5sqNqxpYD 8cNYS1xu6gNqWHsRMQW7v4fbjAanCg==
=ka5q
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ühel kenal päeval, N, 20.01.2022 kell 16:32, kirjutas Brian Evans:

On 1/17/2022 6:24 PM, Georgy Yakovlev 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 bet that the pending polkit merge request[1] (which is just about
ready and blessed but not merged by devs) would seriously drop many
people's concerns over rust.

Using duktape on most systems will suffice for polkit once included.

GNOME and Mozilla products still pull in spidermonkey but other users
will have a much reduced requirement for rust.

librsvg, dev-python/cryptography (masked so far but eventually needs to
move forard, albeit it looks like it won't have as big an impact as it
once would have), probably rather more to come.

Ühel kenal päeval, N, 20.01.2022 kell 20:01, kirjutas Michael Orlitzky:

Avoiding librsvg used to be difficult because it's required by our
GTK
icon packages to render PNGs from SVGs. Luckily dilfridge's binrepo
now makes it easy to download pre-rendered icons, and there's no security/performance/legal concerns with pre-rendered PNGs, so using
them shouldn't present any moral dilemmata. You mainly just have to
replace Firefox, Thunderbird, and GIMP.

And it is required on GTK itself to actually be able to render any SVG
icons. I can not suggest avoiding librsvg with GTK, nor let such
suggestions of such be uncountered.
rust is a toolchain, just like GCC, and if you are running a source-
based distribution, you get to have the toolchains required to compile
from source.


Anyhow, my vote is to default to rust-bin - people can easily be told
to move to dev-lang/rust at their convenience and then explicitly
depclean rust-bin. They can even use system-bootstrap on dev-lang/rust
with rust-bin to do so, in some situations (~arch-only apparently).

Mart

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQKTBAABCgB9FiEEUdZn9pOq0mlNjRvdEKbJ+k9JlgYFAmHqe0ZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDUx RDY2N0Y2OTNBQUQyNjk0RDhEMUJERDEwQTZDOUZBNEY0OTk2MDYACgkQEKbJ+k9J lgb7dQ//YpjmtZtidS+WVJhZOcKFx5MDAAUCzvrz2yi22L8CgXTuTFqVZEXsNcvs 22U/NtQ3glw5GwTVGuMAqVSM6Zkf1o4heM064+l7gC5qSG/94GDSRkYDYT60MFm2 ox55jYoAtVovfbyYTDKUj0UrZa5dnBMTQp6s1hwngszdJmFqJjN5junyJo6sXiWA QLWacDjBBVbJf4cF5ZOtAQdoa3a1xL97OGzJzGhx+h3gNKJjg3mqZr/VPc5Q4XfZ 94MQKIVC6ATS3z1XV2Uiwd2G0nntoW985yfIfO6YOCUyi5HRYsr8Q2Y+LrsrSxZf B2RnB7IcjOtbXBRyV12PsuUvz4iql6fmfW1f0pB1GnX6FDckSHXMq2Da7ZMDxdlv Yj2pFYWWY1wI8Mn8GkAsOy4T1kF+90u4Ryl/BBbxP53h2pUqKy47/IM7z1M7JhmV PWt8Jny6lAby35A1VyZx2JN4sAjQK/g9oU9GAUpr6q0/Bi3UK/sjop50EeGSh+iK Aq744638JzckEqvZlDNMaeqVMKxamA53uFEs2/hjFulIjOTXA+BehK0iEu2HQme+ yC1ZeShkibX7Rb2EGuSWnaQfzfMWwxJEQCJ9J2cUtIj4KRLtGaFR+5NZjG1vBF6F iwbu8mqpjImJyj6Vigyk1DMcWSP69ONl+Hi/gbX+Nffdqc1ODh0=
=jJj8
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Dear Developers,

I like your goal to make Gentoo more user-friendly but Gentoo is a source
based distribution and I dont like binary versions as a default. My question is:

Who has problems with "big" packages like rust or firefox ?

Only User which doesnt know there is a binary version. So, in every case we need to describe it in our AMD64 handbook.

Am Freitag, 21. Januar 2022, 10:22:14 CET schrieb Mart Raudsepp:

Anyhow, my vote is to default to rust-bin - people can easily be told
to move to dev-lang/rust at their convenience and then explicitly
depclean rust-bin.

I am dreaming about another solution where this is not needed:

In our /etc/portage/make.conf we can have a new:

MAKEBIN="rust firefox"

... resulting in an automatic switch to the binary version of all included packages ... of course this is also as recommendation in our AMD64 handbook (with a clue to delete it if not desired).

Kind reagards,
Peter

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 21-01-2022 11:29:54 +0100, Peter Böhm wrote:

Dear Developers,

I like your goal to make Gentoo more user-friendly but Gentoo is a source based distribution and I dont like binary versions as a default. My question is:

Who has problems with "big" packages like rust or firefox ?

Only User which doesnt know there is a binary version. So, in every case we need to describe it in our AMD64 handbook.

Am Freitag, 21. Januar 2022, 10:22:14 CET schrieb Mart Raudsepp:

Anyhow, my vote is to default to rust-bin - people can easily be told
to move to dev-lang/rust at their convenience and then explicitly
depclean rust-bin.

I am dreaming about another solution where this is not needed:

In our /etc/portage/make.conf we can have a new:

MAKEBIN="rust firefox"

... resulting in an automatic switch to the binary version of all included packages ... of course this is also as recommendation in our AMD64 handbook (with a clue to delete it if not desired).

or ... if we could have Portage check the requirements for building a
package, and if it cannot be met, that it tries to resolve the || case,
which would be the -bin variant in this case.

Not sure if the information is available to Portage at dependency
resolution time though.

Fabian

Kind reagards,
Peter

--
Fabian Groffen
Gentoo on a different level

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEELUvHd/Gtp7LaU1vuzpXahU5EQpMFAmHqjEkACgkQzpXahU5E QpOJRggAgF9/u2KxaPQe4fz6ZCBI7LR8KrqHRgQvNvd3d8hM4XCUj8+u6OVlsGkb PSM4xygOhXUwcovIkM/R1RdNipKj3O06vax/vhoUc4+JthE4gS8YyQrSTQDWbr/d 0tU6kzKraAml8TrcO8SBGBnEDHf2/cwGn3TvYxo+zQ5l5MEkaJ82qOw0+06EOL8O 9aum0y3Pjp09PMpWtzqbjgQ9bBaACkTy/wGrusgh7OSaxhaiIISeNWATPoP5AKjo 15F8+On0fVC8ryjNbzFWfu0aLIZW3NaUWgr4rP0S9iCjcML/89njBKvidUNNFdwX 0xuZyhPsAVWVLNLqPcp28ezXOf1tWQ==
=A20s
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Jan 17, 2022 at 3:24 PM 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.

What does this actually mean? Can we more clearly document the negatives?

Is it that Rust takes a long time to build? This seems like just a
consequence of a sourced based distribution. Many things take a long
time to build. I suspect rust is not the only package and again we are
back to staffing binhost like projects for much of the tree so that
this particular complaint can be mitigated, not just for rust, but for
any package.

Is it that Rust build fails because users lack the resources to build
it? We should be using check-reqs here to detect this pre-build and
give the user choices (like telling them rust can't be compiled from
source on their machine and to use rust-bin.)

I tend to empathize more with Peter Böhm later in the thread, in that
Gentoo is sourced based and I'd expect portage to be installing things
from source by default. Building from source is resource intensive and expensive, yes. I think if you want a binary-based distro you are
using the wrong distro at the moment.

-A

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.

Thanks!

--
Georgy

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 1/20/2022 16:32, Rich Freeman wrote:

On Thu, Jan 20, 2022 at 4:10 PM Piotr Karbowski <slashbeast@gentoo.org> wrote:

Ideally we'd have some way to mark binary packages with new EAPI and
have FEATURES flag like 'prefer-binary' and go with -bin in case there's
|| ( ) dependencies list, regardless of the original order in virtual.
This way everyone could be happy and not choose one workflow over another.

Ideally we'd just have a repository of binary builds for everything
with default USE flags for a few profiles, and users could choose to configure portage to just download the binary package if the flags
match, and of course this could be overridden per-package. Then there
would be no need for -bin anything. We have to maintain half of that
for the stage builds anyway.

[snip]

I've learned from running FreeBSD on some of my network equipment that this
is the path they take. They have flags called USES on their Ports system,
and for binary packages, defaults are selected and used for building binary packages. In a handful of cases, such as mtr, they'll offer both an X11-enabled version as well as a non-X11 version of the binpkg. For all
other cases, it's fairly straight forward to build a few packages yourself
via Ports with your own USES selections. E.g., I don't need python support
in bind-tools, so I build that one on my appliances myself to reduce the required dependencies that need to be installed.

--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
rsa6144/5C63F4E3F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943

"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)