1 |
Hi JC, |
2 |
|
3 |
You can add per-package accept keywords to particular packages in the same manner as per-package use flags: |
4 |
1. mkdir $EPREFIX/etc/portage/package.accept_keywords |
5 |
2. create files in there with per-atom definitions like this: |
6 |
=app-text/dos2unix-6.0.6 ** |
7 |
|
8 |
3. Now if you try to emerge the package it will ignore the keyword restrictions and try to install it anyways. |
9 |
|
10 |
Alternatively you can setup an overlay, copy the existing ebuilds into it and modify them so that they work under OS X. |
11 |
|
12 |
John |
13 |
|
14 |
On Jan 6, 2015, at 8:15 AM, JC D <mail2jcdx@×××××.de<mailto:mail2jcdx@×××××.de>> wrote: |
15 |
|
16 |
Hi Jeremy, |
17 |
|
18 |
Yes it helps ;-) |
19 |
I checked Macports and found that all my favourite packages are available there. For productivity reasons I have to think about using macports again or give homebrew a try. |
20 |
|
21 |
The installation problems are mostly related to some basic packages such as lisp packages sbcl and gcl. |
22 |
It wasn't even possible to install emacs. |
23 |
However, if helps to improve gentoo_prefix I will go on ;-) |
24 |
|
25 |
Could please tell me where exactly I have to add the keyword? "(just add the keyword and it will work)" |
26 |
You mean in my make.conf? Or how where do I have to add so it will be applied to a certain package. |
27 |
|
28 |
Thank you! |
29 |
|
30 |
|
31 |
|
32 |
|
33 |
Jeremy Olexa <darkside@g.o<mailto:darkside@g.o>> schrieb am 4:35 Montag, 5.Januar 2015: |
34 |
|
35 |
|
36 |
|
37 |
|
38 |
Hi JC, |
39 |
|
40 |
On Sun, Jan 4, 2015 at 10:54 AM, JC D <mail2jcdx@×××××.de<mailto:mail2jcdx@×××××.de>> wrote: |
41 |
> Hi Group! |
42 |
> |
43 |
> I am using gentoo_prefix on a Mac OS 10.10. |
44 |
> |
45 |
> I am trying to install some packages, especially scientific stuff like |
46 |
> maxima/wxmaxima, paraview and mayavi. |
47 |
> None of these packages works right now and I suspect a major problem with my |
48 |
> gentoo_prefix. |
49 |
> The process fails and one of the messages is: "Darwin patch set |
50 |
> 'darwin-conf' failed to apply!" |
51 |
> What does this mean? Is this an "error" of the ebuild or do I have some |
52 |
> configuration problem on my system that need to be fixec? |
53 |
|
54 |
There is probably no problem with your Gentoo Prefix installation. It |
55 |
looks like you are trying to install some packages that have never |
56 |
been tested and/or ported to to x64-macos architecture. You will have |
57 |
various levels of success here, ranging from easy (just add the |
58 |
keyword and it will work) to very difficult (rewrite the poorly |
59 |
written scientific package build system to support an offset). At |
60 |
least, if the package exists in Macports, it has some chance of |
61 |
success in Gentoo Prefix :) |
62 |
|
63 |
> My ACCEPT_KEYWORDS ist "~x64-macos". Does this mean I am using a "unstable" |
64 |
> branch? (This is not from my make.conf) |
65 |
|
66 |
Actually, there is no 'stable' concept in Gentoo Prefix. You are |
67 |
always using latest version of packages. The Gentoo Prefix team simply |
68 |
does not have the staff to maintain different stable/unstable trees. |
69 |
It normally works out pretty well by leveraging some of the work of |
70 |
Gentoo Linux developers and rely on the fact that massively broken |
71 |
packages do not appear in ~arch on a often. |
72 |
|
73 |
> I am asking, because I could e.g. not install eselect-opengl-1.3.1 but I |
74 |
> after masking this version I could emerge eselect-opengl-1.2.7 without |
75 |
> problems. |
76 |
|
77 |
Hard to say the problem with the latest version. Did you look at the |
78 |
bug tracker or file an issue? |
79 |
|
80 |
|
81 |
> Would it be possible to set ACCEPT_KEYWORDS="+x64-macos" to switch to the |
82 |
> stable branch? And how do I have to reemerge my system in case I do this? |
83 |
> |
84 |
> I am a little desperate because I would like to use gentoo_prefix as a |
85 |
> replace for Macports. However, right now I get no package installed. |
86 |
> Please let me know which information you need. Right now I do not know where |
87 |
> to start... |
88 |
|
89 |
|
90 |
If you have successfully bootstrapped, you actually have several |
91 |
packages installed :) |
92 |
|
93 |
Hope that helps a little bit, |
94 |
Jeremy |