1 |
Hello Meino, |
2 |
|
3 |
On Wed, 01 Nov 2017, tuxic@××××××.de wrote: |
4 |
[..] |
5 |
>But it seems, that I am doing something wrong with the local |
6 |
>overlay... |
7 |
|
8 |
I assumed you already have one. If not, drop this into your |
9 |
/etc/portage/repos.conf/ directory as e.g. local.conf: |
10 |
|
11 |
==== /etc/portage/repos.conf/local.conf ==== |
12 |
[local] |
13 |
location = /usr/local/portage |
14 |
masters = gentoo |
15 |
auto-sync = no |
16 |
priority = 99 |
17 |
==== |
18 |
|
19 |
Or, if you have a _FILE_ /etc/portage/repos.conf, add the above |
20 |
snippet as a new section in there. |
21 |
|
22 |
And create /usr/local/portage. |
23 |
|
24 |
>I copied (as root) |
25 |
> |
26 |
>cp -a /usr/portage/media-gfx/structur-synth /usr/local/portage/media-gfx/. |
27 |
|
28 |
Did you create /usr/local/portage/media-gfx/ before? |
29 |
|
30 |
Clean up /usr/local/portage/media-gfx first, then use: |
31 |
|
32 |
# mkdir -p /usr/local/portage/media-gfx/ |
33 |
# cp -va /usr/portage/media-gfx/structure-synth \ |
34 |
/usr/local/portage/media-gfx/ |
35 |
|
36 |
Depending on your umask, you might need to make stuff explicitly |
37 |
readable for or owned by the user "portage" (usually). |
38 |
|
39 |
# chown -cR portage.portage /usr/local/portage/ |
40 |
|
41 |
Anyway, this should get you a structure like: |
42 |
|
43 |
/usr/local/portage/media-gfx/structure-synth/ |
44 |
/usr/local/portage/media-gfx/structure-synth/metadata.xml |
45 |
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild |
46 |
/usr/local/portage/media-gfx/structure-synth/Manifest |
47 |
|
48 |
Then: |
49 |
|
50 |
# mkdir /usr/local/portage/media-gfx/structure-synth/files |
51 |
|
52 |
drop my '.patch' into that ./files/ dir, drop my -r1.ebuild into |
53 |
/usr/local/portage/media-gfx/structure-synth/ |
54 |
|
55 |
and run: |
56 |
|
57 |
# pushd /usr/local/portage/media-gfx/structure-synth/ |
58 |
# repoman -v manifest |
59 |
# popd |
60 |
|
61 |
(I forgot that step in my first mail) |
62 |
|
63 |
It should look like this then: |
64 |
|
65 |
/usr/local/portage/media-gfx/structure-synth/ |
66 |
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild |
67 |
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0-r1.ebuild |
68 |
/usr/local/portage/media-gfx/structure-synth/files |
69 |
/usr/local/portage/media-gfx/structure-synth/files/structure-synth-1.5.0-gl.patch |
70 |
/usr/local/portage/media-gfx/structure-synth/metadata.xml |
71 |
/usr/local/portage/media-gfx/structure-synth/Manifest |
72 |
|
73 |
(actually, you could prune the structure-synth-1.5.0.ebuild file, |
74 |
update the manifest again if you do). |
75 |
|
76 |
>then |
77 |
> |
78 |
>eix structure-synth |
79 |
> |
80 |
>* media-gfx/structure-synth |
81 |
> Available versions: (~)1.5.0 |
82 |
> Homepage: http://structuresynth.sourceforge.net/ |
83 |
> Description: A program to generate 3D structures by specifying a design grammar |
84 |
> |
85 |
>so no *-r1 version visible. |
86 |
|
87 |
Did you run 'eix-update'??? *nudge* *nudge* |
88 |
|
89 |
Anyway: even without eix-update and eix not showing stuff, |
90 |
|
91 |
# emerge --pretend --nodeps media-gfx/structure-synth |
92 |
|
93 |
should show that it'd build media-gfx/structure-synth-1.5.0-r1::local |
94 |
|
95 |
(unless I forgot something about initializing a local overlay, it's |
96 |
been a while). |
97 |
|
98 |
>layman -l does not show up structure-synth |
99 |
|
100 |
That lists overlays. Not packages inside them. |
101 |
|
102 |
>Then I tried different permutations of "media-gfx" (w/o) and |
103 |
>structur-synth in combination with layman -a in desperation ;) |
104 |
>no success |
105 |
|
106 |
layman and your local overlay have nothing to do with each other. |
107 |
layman is "just" a tool to easily add/remove "external" public |
108 |
overlays. And eix-layman to add/remove them to/from your local |
109 |
'eix'-DB and what is considered "local" ('eix' vs. 'eix -R'). |
110 |
|
111 |
[..] |
112 |
>So I think, that the layman engine is working correctly so far. |
113 |
>But the driver behind the steering wheels needs some instructions it |
114 |
>seems.... ;) |
115 |
>Where can I get my license? |
116 |
|
117 |
In the handbook, IIRC :) I did read that about a local overlay in the |
118 |
official docs somewhere (and my local overlay is over 100 pkgs ;) |
119 |
|
120 |
PS: I wonder how that ebuild got into the portage-tree ... Maybe some |
121 |
weird configs present or absent in the qt4/qmake stuff about opengl... |
122 |
|
123 |
I found that 'QMAKE_LIBS_OPENGL="-lGL"' thingy I added (with the |
124 |
missing '-lGLU') to the ebuild in the qmake config files in |
125 |
/usr/share/qt4/... I hate qmake (and just about every other build |
126 |
system[1]). |
127 |
|
128 |
Ask, if stuff is still unclear. And read up a bit again on overlays |
129 |
and layman ;) |
130 |
|
131 |
HTH, |
132 |
-dnh |
133 |
|
134 |
[1] had a problem recently with some stuff using scons. Needed |
135 |
'strace' to find why it did not pick up some header or lib. |
136 |
*gah* As bad as the autotools or plain Makefiles may be, they're |
137 |
at least transparent and easy to grep around in and _local_ to |
138 |
the package. |
139 |
|
140 |
-- |
141 |
Thank God I'm an atheist. |