1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Apr 7, 2005, at 7:04 AM, Brian Harring wrote: |
5 |
|
6 |
> [1] Yes, exceptions occur. Replacing sed (which works in the context |
7 |
> of the osx os) because we label it as deficient doesn't qualify, nor |
8 |
> despite my hatred of it, does replacing libtoolize with a gnu equiv |
9 |
> that sucks substantially less qualify. |
10 |
|
11 |
In the cases where a particular tool is truly inadequate our precedence |
12 |
has been to install a second version of the tool under a prefixed name |
13 |
(as with sed). In terms of libtoolize, Apple provides "glibtoolize" |
14 |
which AFAIK is the gnu equivalent. As far as I've seen it "sucks less" |
15 |
enough to be workable. |
16 |
|
17 |
The point is that in cases where tools just won't work for our purposes |
18 |
there are workarounds that do not involve overwriting the native tools |
19 |
that are expected by the system to be there. |
20 |
|
21 |
- --Lina Pezzella |
22 |
Ebuild/Porting Co-Lead |
23 |
Gentoo for Mac OS X |
24 |
-----BEGIN PGP SIGNATURE----- |
25 |
Version: GnuPG v1.4.1 (Darwin) |
26 |
|
27 |
iD8DBQFCVWSVNJ9STR9DbYERAu4XAJwKFGXNmw4MCLp9p9Dluw/OlJO6mgCfWZA9 |
28 |
ZsH5hY/AdvZunVvIpKdfNVk= |
29 |
=k1DU |
30 |
-----END PGP SIGNATURE----- |
31 |
|
32 |
-- |
33 |
gentoo-dev@g.o mailing list |