1 |
Just wanted to put my 2cent into the discussion. |
2 |
I suppose I am currently just a pure Gentoo-OSX user, and while I see the |
3 |
point of the prefix project, I am not really convinced by it. I like the |
4 |
way Gentoo integrates into the system, or at least the part accessible by |
5 |
a console. |
6 |
|
7 |
I see this as an advantage above e.g. Fink, with its own namespace. The |
8 |
namespace variant implies that I have to fudge around with PATH variables |
9 |
and other CLI stuff, in order to get the apps working. I still have no |
10 |
real MacOSX integration, with App folder and GUI starter elements (which |
11 |
would be my biggest feature request) |
12 |
|
13 |
>From what I see as a user, the Gentoo packages divide into 4 categories |
14 |
|
15 |
1) packages which integrate nicely into the system (no dependencies, or |
16 |
dependencies which are properly provided by MacOS) |
17 |
2) packages which clash with MacOS provided packages, things like python |
18 |
or automake spring to mind |
19 |
3) packages which depend on 2) |
20 |
4) misc packages which are otherwise problematic. This means most of the |
21 |
package.masked packages, where I cannot really speak about. |
22 |
|
23 |
The biggest problem is obiously the packages in 2) |
24 |
|
25 |
My private idea in order to emerge packages in 3) would currently be to |
26 |
manually install the needed packages in places like /usr/local (instead of |
27 |
Gentoos /usr) and put these packages into package.provided. It would be |
28 |
really nice if I could use this way while still being able to use the |
29 |
emerge functionaltiy. Perhaps this could be handled by a special USE flag? |
30 |
|
31 |
Regards |
32 |
Dirk |
33 |
|
34 |
-- |
35 |
gentoo-osx@g.o mailing list |