1 |
Diego 'Flameeyes' Pettenò wrote: |
2 |
> On Sunday 06 November 2005 21:10, Grobian wrote: |
3 |
>> My opinion actually was to just let it be ~ppc-macos, since there are no |
4 |
>> known problems with the OS provided find and xargs. When we have a |
5 |
>> prefix, we can just install the normal GNU find and xargs (without g |
6 |
>> prefix) and have maximum compatibility with the other arches on that point. |
7 |
> I think you shouldn't install it non-prefixed. |
8 |
> Reasoning? You change the expected environment for also Portage, that |
9 |
> currently uses GNU userland to identify find and xargs commandline. |
10 |
|
11 |
I agree with you, but I don't follow your reasoning. Portage IMHO |
12 |
expects it's own (GNU) find and xargs. Or well, not Portage, but devs |
13 |
that just create ebuilds on Gentoo Linux and don't mind about your bugs |
14 |
for sticking to a common subset of supported flags. |
15 |
|
16 |
> The tree is already safe for find and xargs syntax, and there are no big deal |
17 |
> in using GNU's or BSD's find and xargs to ebuilds. |
18 |
> There are for users, tho, but letting them use GNU find without knowing is, |
19 |
> IMHO, an error. |
20 |
> Allowing an user to select gfind explicitely is another story. |
21 |
|
22 |
Which would be the case if we would include it in the base install. |
23 |
Since we don't override anything, we simply add it as g*. The alias sed |
24 |
-> gsed is only used in Portage itself, it's *not* set in the global |
25 |
profile for the user. |
26 |
|
27 |
> For what it's worth, the userland-gnu ebuild installs /usr/libexec/gnu links |
28 |
> for GNU tools, also cp, mv, make, find and so on. Putting that in $PATH |
29 |
> allows users to have interactive shells using GNU userland without having to |
30 |
> do hacks around. |
31 |
|
32 |
Which is nice. Why don't we (OSX) use this ebuild? (If it indeed does |
33 |
what I think it does.) |
34 |
|
35 |
> Remember that compatibility is *not* only with Gentoo Linux, we should try to |
36 |
> minimize the difference between Gentoo/ALT projects, too. |
37 |
|
38 |
This is currently being made somewhat different because there are three |
39 |
flavours of Gentoo Alt systems. Maybe you and I should have a chat on |
40 |
outlining this. |
41 |
|
42 |
> If you start shipping in prefixes the GNU tools, people would start telling |
43 |
> other Gentoo/ALT ports to do so, and I for one don't want that, as I'd rather |
44 |
> see Gentoo/*BSD ports to use their own userland where applicable. |
45 |
> For design decisions, such as "should we use the default or not", gentoo-alt |
46 |
> is the place, don't take one-sided decisions or you'll repeat the errors for |
47 |
> which many devs blames the Gentoo for Mac OSX project and Gentoo/ALT project |
48 |
> entirely. |
49 |
|
50 |
Then this rather innocent email I started this thread with, turns out to |
51 |
be a the cause of a valuable conclusion, that you and I need to do some |
52 |
work on this subject. |
53 |
|
54 |
|
55 |
-- |
56 |
Fabian Groffen |
57 |
Gentoo for Mac OS X Project -- Interim Lead |
58 |
-- |
59 |
gentoo-osx@g.o mailing list |