Hello Meino,
On Wed, 01 Nov 2017, tu...@posteo.de wrote:
[..]
>But it seems, that I am doing something wrong with the local
>overlay...
I assumed you already have one. If not, drop this into your
/etc/portage/repos.conf/ directory as e.g. local.conf:
==== /etc/portage/repos.conf/local.conf ====
[local]
location = /usr/local/portage
masters = gentoo
auto-sync = no
priority = 99
====
Or, if you have a _FILE_ /etc/portage/repos.conf, add the above
snippet as a new section in there.
And create /usr/local/portage.
>I copied (as root)
>
>cp -a /usr/portage/media-gfx/structur-synth /usr/local/portage/media-gfx/.
Did you create /usr/local/portage/media-gfx/ before?
Clean up /usr/local/portage/media-gfx first, then use:
# mkdir -p /usr/local/portage/media-gfx/
# cp -va /usr/portage/media-gfx/structure-synth \
/usr/local/portage/media-gfx/
Depending on your umask, you might need to make stuff explicitly
readable for or owned by the user "portage" (usually).
# chown -cR portage.portage /usr/local/portage/
Anyway, this should get you a structure like:
/usr/local/portage/media-gfx/structure-synth/
/usr/local/portage/media-gfx/structure-synth/metadata.xml
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild
/usr/local/portage/media-gfx/structure-synth/Manifest
Then:
# mkdir /usr/local/portage/media-gfx/structure-synth/files
drop my '.patch' into that ./files/ dir, drop my -r1.ebuild into
/usr/local/portage/media-gfx/structure-synth/
and run:
# pushd /usr/local/portage/media-gfx/structure-synth/
# repoman -v manifest
# popd
(I forgot that step in my first mail)
It should look like this then:
/usr/local/portage/media-gfx/structure-synth/
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0.ebuild
/usr/local/portage/media-gfx/structure-synth/structure-synth-1.5.0-r1.ebuild
/usr/local/portage/media-gfx/structure-synth/files
/usr/local/portage/media-gfx/structure-synth/files/structure-synth-1.5.0-gl.patch
/usr/local/portage/media-gfx/structure-synth/metadata.xml
/usr/local/portage/media-gfx/structure-synth/Manifest
(actually, you could prune the structure-synth-1.5.0.ebuild file,
update the manifest again if you do).
>then
>
>eix structure-synth
>
>* media-gfx/structure-synth
> Available versions: (~)1.5.0
> Homepage: http://structuresynth.sourceforge.net/
> Description: A program to generate 3D structures by specifying a
> design grammar
>
>so no *-r1 version visible.
Did you run 'eix-update'??? *nudge* *nudge*
Anyway: even without eix-update and eix not showing stuff,
# emerge --pretend --nodeps media-gfx/structure-synth
should show that it'd build media-gfx/structure-synth-1.5.0-r1::local
(unless I forgot something about initializing a local overlay, it's
been a while).
>layman -l does not show up structure-synth
That lists overlays. Not packages inside them.
>Then I tried different permutations of "media-gfx" (w/o) and
>structur-synth in combination with layman -a in desperation ;)
>no success
layman and your local overlay have nothing to do with each other.
layman is "just" a tool to easily add/remove "external" public
overlays. And eix-layman to add/remove them to/from your local
'eix'-DB and what is considered "local" ('eix' vs. 'eix -R').
[..]
>So I think, that the layman engine is working correctly so far.
>But the driver behind the steering wheels needs some instructions it
>seems.... ;)
>Where can I get my license?
In the handbook, IIRC :) I did read that about a local overlay in the
official docs somewhere (and my local overlay is over 100 pkgs ;)
PS: I wonder how that ebuild got into the portage-tree ... Maybe some
weird configs present or absent in the qt4/qmake stuff about opengl...
I found that 'QMAKE_LIBS_OPENGL="-lGL"' thingy I added (with the
missing '-lGLU') to the ebuild in the qmake config files in
/usr/share/qt4/... I hate qmake (and just about every other build
system[1]).
Ask, if stuff is still unclear. And read up a bit again on overlays
and layman ;)
HTH,
-dnh
[1] had a problem recently with some stuff using scons. Needed
'strace' to find why it did not pick up some header or lib.
*gah* As bad as the autotools or plain Makefiles may be, they're
at least transparent and easy to grep around in and _local_ to
the package.
--
Thank God I'm an atheist.
