Re: Enabling Binaries by default in Stage3s

Hi everyone!

Have been reading through this thread for the last few days, and wanted to say a few stuff

I personally don't think that any changes are really needed per se, and here's my reasoning:

In the Handbook for AMD64, https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Installing_binary_packages
everyone can see that It has a section for binary packages, be it a new user who's just getting into Gentoo and
installing the system using the Handbook (which they should), or be it someone else who's just reinstalling Gentoo after
a while and need to refresh their memory

The current way simply just works, it doesn't break pre-existing tooling and automation, while it also gives people
options to not compile their system from source, and also informs new users that "yes, you can also use binaries"

while people on both sides have given their takes, and I'm just regurgitating a bit, what I do think that in the end, it
is up to the user themselves to follow the proper guide, and if they follow the proper guide, they will get informed
about binary packages, and if they wanna do it, they can just simply do it, and if they don't wanna do it, they can
ignore that step

Hence, yes. I personally think that enabling binaries by default will cause confusion and as others have pointed out, it
will break existing tooling. I also do think the other two options that dale recommended in (sorry I don't have the
exact timestamps, had to reply to this thread manually it's a long story):

> Gentoo is about choice, always has been.  A couple options I see. Have a 
> stage3 tarball for compile from source users and another for binary 
> users.  Each one comes set up to use the method of install the user 
> wants.  Second possibility.  Have a tarball, just one, that once 
> unpacked and chrooted into, one can type in a command and select which 
> method they want to use, this should be able to automate for those using 
> scripts as well.  The eselect command comes to mind but there may be 
> other methods or even better ideas on that.  From there on, it uses the 
> method the user wants.  There may be other ways that occur to others as 
> well that may even work better than one of those.

Is also either not needed, or complicates stuff.

For example, the first option with two tarballs would be basically the same thing, except for a single line in make.conf
ig.

And the second option, where it's a single tarball, but you can type a command, complicates more stuff, eg: will the
command be optional? Or will the command be required to proceed the installation?

If the command is optional, then we go
circle back this again where we need to discuss what will be enabled by default, and if it's optional anyway, then it's
basically the same thing that Gentoo is doing right now. An optional thing that you can do in the installation process,
which the Handbook will inform the user about in the installation guide

And if the command isn't optional, then it also breaks existing tooling and scripts that expect the installation process
to go in a certain stable replicatable way without major breaking changes. eg: i have my own scripts and config setup
which declaratively sets up my machines, and if suddenly the installation process requires something to change my
scripts and configs, it will be a bit of an annoyance. And one can imagine the issues where it would require already
existing tooling changes

Anyways, that will be all. Just wanted to share my own thoughts.

Regards,
ingenarel :3

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEaVHGjxYJKwYBBAHaRw8BAQdA2Sn1x0Q3XVbY8J1gfcWIwDMQY0dwlU84Rdr+
xgRCtmy0NWluZ2VuYXJlbCAoTmVvSmVzdXMpIDxpbmdlbmFyZWxfbmVvamVzdXNA
ZGlzcm9vdC5vcmc+iJAEExYKADgWIQQ75gPOuW3nKwEUEmV5KLSKFzukAAUCaVHG
jwIbAwULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRB5KLSKFzukAJiUAQDO8LgQ
Pf1GQcqTtdVUKUk3QJWD4mV4rixlc+OelrWHzQEAqYQB9t012TLnQiewUhbe0gYZ
9S0ZMQN7eGTQvcntHA24OARpUcaPEgorBgEEAZdVAQUBAQdAntIkfd6jLMQKVSuP
Ep7RGHNIdd5QBPAa0Sn1/uF9bFADAQgHiHgEGBYKACAWIQQ75gPOuW3nKwEUEmV5
KLSKFzukAAUCaVHGjwIbDAAKCRB5KLSKFzukAFGSAQDQHe3eExLfVv0bIzDTEHpK
fA9nWTF9F7jsMVLviNC5wgD/W02Zr7/+R/8H45+7eS7DxAvGQf/ehEow/dH91lpa
kQ8=
=y8x6
-----END PGP PUBLIC KEY BLOCK-----

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

iLEEABYKAFkWIQQ75gPOuW3nKwEUEmV5KLSKFzukAAUCanxLJBsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIfHGluZ2VuYXJlbF9uZW9qZXN1c0BkaXNyb290Lm9y
ZwAKCRB5KLSKFzukAK5rAQCbazUHPSiXpWszm2bi5vDETWfsXax84bXghkVi8noB
SAD/XmyUlupWVvReZzetiEM/LPP/6nsydz7RuiajHQbBQAI=
=eMpC
-----END PGP SIGNATURE-----