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