1 |
On Thu, Apr 07, 2005 at 11:22:49AM +0100, Stroller wrote: |
2 |
> On Apr 7, 2005, at 7:33 am, Luca Barbato wrote: |
3 |
> >Brian Harring wrote: |
4 |
> >>Problem with the preference you have above is you're considering |
5 |
> >>portage as the primary pkg manager/authority for that system, which it |
6 |
> >>isn't on osx. |
7 |
> >If a tool is broken you change it, the apple toolchain and probably |
8 |
> >userspace could enjoy some improvements. |
9 |
> |
10 |
> Do you actually use OS X? |
11 |
> |
12 |
> This is not a case of sed being broken on BSD / OS X - on a Mac |
13 |
> everything works fine out of the box, and users can use standard tools, |
14 |
> many of which are provided, just like on any other *NIX. This is a case |
15 |
> where the use of Gentoo would make compiling packages easier & more |
16 |
> convenient for OS X users, and Gentoo prefers a non-standard tool; the |
17 |
> Apple install is not "broken" and many people would not consider |
18 |
> messing with it to be beneficial. |
19 |
|
20 |
While I'm sure I'm going to get shot by the various people who label |
21 |
the osx toolchain as broken... well. |
22 |
|
23 |
tough cookies. |
24 |
|
25 |
One thing aparently ignored is the implication of my earlier |
26 |
"portage is the secondary manager comment"- the logic of just flat |
27 |
out replacing osx binaries/libs with gentoo replacements --will-- |
28 |
result in one utterly screwed up system when the user upgrades from |
29 |
10.3 to 10.4. |
30 |
|
31 |
You know apple ain't going to support the broken mess that results, |
32 |
and nor will we most likely. That is why we can't go replacing |
33 |
whatever we label as broken[1] on *any* system where portage is |
34 |
secondary. |
35 |
|
36 |
[1] Yes, exceptions occur. Replacing sed (which works in the context |
37 |
of the osx os) because we label it as deficient doesn't qualify, nor |
38 |
despite my hatred of it, does replacing libtoolize with a gnu equiv |
39 |
that sucks substantially less qualify. |
40 |
~brian |
41 |
-- |
42 |
gentoo-dev@g.o mailing list |