| 1 |
On 02/02/2017 10:06 AM, Kristian Fiskerstrand wrote: |
| 2 |
> On 02/02/2017 03:11 PM, Michael Orlitzky wrote: |
| 3 |
>> Can we discourage IUSE defaults except for #1 and #2? I'm equally guilty |
| 4 |
>> of #3 and #4, but I now regret them. I would also like to see |
| 5 |
>> explanations in metadata.xml of why +flags are on by default. |
| 6 |
> |
| 7 |
> This presumes that the goal is minimal system in all cases, rather than |
| 8 |
> a good user experience for inter alia a desktop system or a |
| 9 |
> server-system. If a user requires a minimal system for whatever reason |
| 10 |
> (s)he is likely more prepared to understand the choices than the average |
| 11 |
> user. |
| 12 |
|
| 13 |
Not so sure about his postulate. |
| 14 |
|
| 15 |
As one who defaults to minimal systems (yes even on a 8-core 32G ram |
| 16 |
system), I'd like to offer a bit of insight. Please keep in mind that |
| 17 |
in my experiences, there are probably many more folks creating ebuilds |
| 18 |
than gentoo has devs; so as logical and streamlined and coherent as |
| 19 |
possible means a necessary focal point is the minimized gentoo system build. |
| 20 |
|
| 21 |
Some folks need a minimal install because of their hardware constraints. |
| 22 |
|
| 23 |
Some folks want a minimal install because statistically that's the |
| 24 |
easiest way to get a new (rolling) distro working, especially minus a |
| 25 |
heavy WM, like KDE. Due to a lack of a streamlined installer processes |
| 26 |
for gentoo, there is a lot of 'monkey see monkey do' approaches to |
| 27 |
repetitively installing gentoo in the wild, so a minimal focus is |
| 28 |
better. (KISS is king). |
| 29 |
|
| 30 |
Some folks want a minimal install, because it's fairly trivial (for |
| 31 |
identical platformed system) to then copy over bin packages or compile |
| 32 |
in additional packages (via the world file) and make the system |
| 33 |
whatever they want it to be. It can also be returned to a minimal state, |
| 34 |
by just removing these secondary packages that converted the minimal |
| 35 |
system into something more full featured. |
| 36 |
|
| 37 |
Some folks want a minimal arm system that is in the footprint of a small |
| 38 |
(arm-based) laptop, so it is quite similar to Single Board Computer arm |
| 39 |
systems as possible; ultimately trying to keep a variety of arm systems |
| 40 |
as similar as possible. |
| 41 |
|
| 42 |
Some folks have a variety of embedded gentoo systems, and the closer the |
| 43 |
minimal system is to being identical (via package sets) the more logical |
| 44 |
their schema can be on management (think IoT). |
| 45 |
|
| 46 |
|
| 47 |
I could go on and on all all, clusters, firewalls kiosk etc etc. My |
| 48 |
point is a minimal system is the foundational building block for gentoo |
| 49 |
and as such it is like a construction dock for building up all sorts, if |
| 50 |
not all gentoo systems. |
| 51 |
|
| 52 |
How this affects re-organization of documentation on IUSE and related |
| 53 |
issues is of great curiosity to me. So, when my work is complete (or at |
| 54 |
least enough to share) there shall be many stage-4 minimal gentoo images |
| 55 |
to install from and go from there. So as much as all issues can be |
| 56 |
minimized, standardized, documented and look like other arches, the "mo |
| 57 |
better" imo. |
| 58 |
|
| 59 |
|
| 60 |
hth, |
| 61 |
James |
Archives