| 1 |
Finn Thain wrote: |
| 2 |
> On Sat, 5 Nov 2005, Nick Dimiduk wrote: |
| 3 |
> |
| 4 |
>> Grobian wrote: |
| 5 |
>>> I thought let's give it a shout, because maybe we should add it to the |
| 6 |
>>> base profile somehow and alias some more to have calls to find and |
| 7 |
>>> xarg (when not in a pipe) being directed to gfind and gxargs for |
| 8 |
>>> maximum compatibility. Maybe it's not worth it. Opinions? |
| 9 |
>> How big is the installation of findutils? If it's not gigantic (I don't |
| 10 |
>> expect it to be) then I think this is a good idea. Keeping things |
| 11 |
>> within the portage environment as similar to "mainline" as possible will |
| 12 |
>> only avoid hassles. |
| 13 |
> |
| 14 |
> If by "mainline", you mean "Gentoo/Linux", the major dis-similarity |
| 15 |
> remaining is the name of the executable. |
| 16 |
> |
| 17 |
> IMHO, the Alt project policy of mandatory "g" prefixes is misguided. If it |
| 18 |
> suits BSD, great, but AFAICT it limits portability to non Gentoo systems, |
| 19 |
> and it shouldn't be applied to all -alt projects. |
| 20 |
|
| 21 |
My opinion actually was to just let it be ~ppc-macos, since there are no |
| 22 |
known problems with the OS provided find and xargs. When we have a |
| 23 |
prefix, we can just install the normal GNU find and xargs (without g |
| 24 |
prefix) and have maximum compatibility with the other arches on that point. |
| 25 |
|
| 26 |
> The best Alt project policy is to always use portable shell script in the |
| 27 |
> tree. That is, avoid gnu extensions. That would help minimise the base |
| 28 |
> system if nothing else. |
| 29 |
> |
| 30 |
> http://www.gentoo.org/proj/en/gentoo-alt/index.xml |
| 31 |
|
| 32 |
If you can do an easy change to just make it work on non GNU versions -- |
| 33 |
something which Flameeyes has put a lot efforts in -- then I prefer to |
| 34 |
simply do that. However, if problems or limitations (like OSX's sed for |
| 35 |
instance) which are not easy to circumvent, then I'd opt for getting the |
| 36 |
GNU version to avoid making it very complicated for everyone. |
| 37 |
|
| 38 |
Question that remains is whether we can use the OS provided tools |
| 39 |
without having to lie against portage, or limiting portage to 'upgrade' |
| 40 |
(override) them with 'newer' (other?) versions when necessary. |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
Fabian Groffen |
| 45 |
Gentoo for Mac OS X Project -- Interim Lead |
| 46 |
-- |
| 47 |
gentoo-osx@g.o mailing list |
Archives