1 |
On Thu, Aug 16, 2012 at 7:05 AM, Rich Freeman <rich0@g.o> wrote: |
2 |
> On Wed, Aug 15, 2012 at 10:04 AM, Fabian Groffen <grobian@g.o> wrote: |
3 |
>> |
4 |
>> From that angle, if you wouldd remove the system set, would you add its |
5 |
>> contents to the Portage ebuild? Portage itself doesn't need a compiler |
6 |
>> or might not need gawk, but whatever it runs (ebuilds) often need so. |
7 |
> |
8 |
> Nope - I'd add them to every ebuild, and only where needed. That's |
9 |
> the whole point. |
10 |
> |
11 |
>> |
12 |
>> Adding libc, a compiler, linker, shell, etc. to almost any every ebuild |
13 |
>> looks pretty much useless to me. Adding deps for all regular tools an |
14 |
>> ebuild uses (bash, sed, awk, cut, wc, ...) seems like error-prone and |
15 |
>> pretty much useless to me as well. So, there is the system set which |
16 |
>> just is the central place where those packages are recorded. |
17 |
> |
18 |
> It is only useful for situations where people want to do something |
19 |
> unusual. Some would argue that this is the only situation where |
20 |
> Gentoo is useful. If I wanted a system just like everybody else's I |
21 |
> guess I'd run Ubuntu, if not Windows or OSX. |
22 |
> |
23 |
> In any case, I do agree that getting there is associated with pain. I |
24 |
> just like to think that getting there "someday" would be nice. I know |
25 |
> that a systematic effort exists in mathematics to try to reduce all of |
26 |
> math to a minimum set of axioms and have everything else be formally |
27 |
> derived. I consider that a thing of beauty, even if I don't care to |
28 |
> read the two volumes necessary to get to 1+1=2. |
29 |
> |
30 |
> Rich |
31 |
> |
32 |
|
33 |
The other point of the system set is to get rid of the chicken and egg |
34 |
problem. For example, virtually every package in the system set ships |
35 |
as a tar, including tar itself. All the compression utilities ship as |
36 |
tars, which need to be installed to build tar (think -z, -j, -J). You |
37 |
need a standard C library to run virtually everything including tar, |
38 |
which you need to extract your standard C sources. The list goes on. |
39 |
|
40 |
|
41 |
-- |
42 |
Doug Goldstein |