1 |
Nikos Chantziaras wrote: |
2 |
> Reading around on the net, it amazes me how many people are using |
3 |
> developer profiles for their Gentoo because they think it's for software |
4 |
> developers and don't see that it's for Gentoo developers and not |
5 |
> intended for end users. They know the "Developer" installation profiles |
6 |
> of other distros and think Gentoo's profiles are just the same (on those |
7 |
> distros, selecting a dev profile just means it installs GCC + dev libs + |
8 |
> IDEs by default.) |
9 |
> |
10 |
> Some kind of warning or other mechanism that does selecting this profile |
11 |
> without knowing what you're doing would be a good idea. |
12 |
> |
13 |
|
14 |
*shrug* If people would _read_ the documentation, such as |
15 |
http://www.gentoo.org/doc/en/gentoo-upgrading.xml or |
16 |
http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=6#doc_chap2, |
17 |
then they would know what the profiles are for. |
18 |
|
19 |
I don't think we should start making certain profiles harder to use. |
20 |
Maybe if profiles.desc had a more explanatory entry on the developer |
21 |
profile so that users know what's up with it. Or better yet, include an |
22 |
entry in the eselect profile module that prints a brief description of a |
23 |
given profile, or at least references the various documentation on profiles. |
24 |
|
25 |
Oh, and FYI, gcc (and complete toolchain) and various development |
26 |
libraries are already installed by default -- that's the nature of using |
27 |
a source-based distro; all that stuff needs to be there to do anything, |
28 |
so it's already included. |
29 |
|
30 |
At no point will merely "selecting a new profile" actually install |
31 |
anything. As always, you have to go through the package manager if you |
32 |
want something installed. |