Le Sun, 5 May 2013 21:39:21 +0200,
Karl Lindén <[email protected]> a écrit :
> You should probably respect EPREFIX in the arguments to emake.
>
> - einfo " /usr/share/doc/${PF}/addons/convert_colorsets"
> + einfo " /usr/share/doc/${PN}/addons/convert_colorsets."
> Is the ebuild installing docs into /usr/share/doc/${PN} despite the
> docdir argument to emake?
The einfo was wrong, I just corrected it. According to the Makefile,
$addondir is $prefix/share/fvwm-crystal/addons, and it is where the
files get installed with my ebuild.
Portage ebuild use $addondir=$prefix/share/doc/${PF}/addons.
It is pro and con with both locations. The files are easier to find for
the user when they are in $prefix/share/doc/${PF}/addons, but they
get compressed by portage, and most of them are scripts or resource
files, not documentation.
Dominique
>
>
> 2013/5/5 <[email protected]>:
> > Revision: 2723
> > Author: dominique
> > Date: 2013-05-05 21:22:33 +0200 (Sun, 05 May 2013)
> > Log Message:
> > -----------
> > fvwm-crystal-9999: removed non needed USE flags; updated to EAPI 5
> > and python-r1
> >
> > Modified Paths:
> > --------------
> > trunk/overlays/proaudio/x11-themes/fvwm-crystal/ChangeLog
> > trunk/overlays/proaudio/x11-themes/fvwm-crystal/Manifest
> > trunk/overlays/proaudio/x11-themes/fvwm-crystal/fvwm-crystal-9999.ebuild
> > trunk/overlays/proaudio/x11-themes/fvwm-crystal/metadata.xml
> >
>
>
--
"We have the heroes we deserve."
