1 |
On Sunday 06 November 2005 21:10, Grobian wrote: |
2 |
> My opinion actually was to just let it be ~ppc-macos, since there are no |
3 |
> known problems with the OS provided find and xargs. When we have a |
4 |
> prefix, we can just install the normal GNU find and xargs (without g |
5 |
> prefix) and have maximum compatibility with the other arches on that point. |
6 |
I think you shouldn't install it non-prefixed. |
7 |
Reasoning? You change the expected environment for also Portage, that |
8 |
currently uses GNU userland to identify find and xargs commandline. |
9 |
|
10 |
The tree is already safe for find and xargs syntax, and there are no big deal |
11 |
in using GNU's or BSD's find and xargs to ebuilds. |
12 |
There are for users, tho, but letting them use GNU find without knowing is, |
13 |
IMHO, an error. |
14 |
Allowing an user to select gfind explicitely is another story. |
15 |
|
16 |
For what it's worth, the userland-gnu ebuild installs /usr/libexec/gnu links |
17 |
for GNU tools, also cp, mv, make, find and so on. Putting that in $PATH |
18 |
allows users to have interactive shells using GNU userland without having to |
19 |
do hacks around. |
20 |
|
21 |
|
22 |
Remember that compatibility is *not* only with Gentoo Linux, we should try to |
23 |
minimize the difference between Gentoo/ALT projects, too. |
24 |
If you start shipping in prefixes the GNU tools, people would start telling |
25 |
other Gentoo/ALT ports to do so, and I for one don't want that, as I'd rather |
26 |
see Gentoo/*BSD ports to use their own userland where applicable. |
27 |
For design decisions, such as "should we use the default or not", gentoo-alt |
28 |
is the place, don't take one-sided decisions or you'll repeat the errors for |
29 |
which many devs blames the Gentoo for Mac OSX project and Gentoo/ALT project |
30 |
entirely. |
31 |
|
32 |
-- |
33 |
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/ |
34 |
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE |