| 1 |
On Sat, 7 Dec 2013, Rich Freeman wrote: |
| 2 |
|
| 3 |
> On Sat, Dec 7, 2013 at 12:52 AM, Rick "Zero_Chaos" Farina |
| 4 |
> <zerochaos@g.o> wrote: |
| 5 |
|
| 6 |
<snip> |
| 7 |
|
| 8 |
>> Honestly, I'm not really sure why anyone would want to make stage3 less |
| 9 |
>> functional than it already is but honestly net isn't something I'm ready |
| 10 |
>> to give up just yet. |
| 11 |
> |
| 12 |
> It isn't about making the stage3 less functional, but about giving the |
| 13 |
> user a choice. We don't stick a kernel in stage3, despite the fact |
| 14 |
> that everybody needs one. We don't stick an MTA in the stage3 despite |
| 15 |
> the fact that one of those is pretty hard to live without. |
| 16 |
> |
| 17 |
> Now that Gentoo apparently offers a wide selection of network |
| 18 |
> managers, perhaps it makes sense to have the user pick which one they |
| 19 |
> want to use. |
| 20 |
> |
| 21 |
> IMHO the purpose of @system and the stage3 is to solve the circular |
| 22 |
> dependency problem inherent in bootstrapping. It really shouldn't |
| 23 |
> contain anything beyond this. By all means have an @useful-utils set |
| 24 |
> or some kind of profile that auto-installs a list of packages like |
| 25 |
> openssh, vim, and so on. However, these are not required to bootstrap |
| 26 |
> a system and I'm not sure why we should be forcing them into the |
| 27 |
> @system set as a result. |
| 28 |
|
| 29 |
I disagree with you about this - stage3 and @system are not the same. |
| 30 |
The purpose of a stage3 is to provide the minimum "sane" environment to do |
| 31 |
an install. We provide some packages because of "convenience". |
| 32 |
So even though someone might not want to connect remotely, there's no |
| 33 |
valid reason to drop openssh from a stage3. Just like we'll keep |
| 34 |
providing nano and less in the stages - they may not be needed, but |
| 35 |
it makes sense to provide them. |
| 36 |
|
| 37 |
> Another option would be to have things installed in the stage3 that |
| 38 |
> are not part of the @system set, so that they would be depcleaned at a |
| 39 |
> later date. I'm not a big fan of that, however, mainly because it |
| 40 |
> could be a curve-ball for somebody to deal with after they think |
| 41 |
> they've gotten everything working. I think users will have a better |
| 42 |
> understanding of how their system is set up if they put things there |
| 43 |
> than if things start out there but get yanked out from under them. |
| 44 |
|
| 45 |
There's an open bug about this - |
| 46 |
https://bugs.gentoo.org/show_bug.cgi?id=393445 |
| 47 |
|
| 48 |
Some of the previous comments are based with this bug in mind. |
Archives