[gentoo-dev] pccts lives in /usr/lib/pccts/*/

[gentoo-dev] pccts lives in /usr/lib/pccts/*/

[Peter Kadau]

hi !
in trying to get cdrdao cleanly compiled from sources
(first step to an ebuild hopefully ;-)
i realized that the binaries and include files of
pccts live in /usr/lib/pccts/*/
imho, one should set up appropriate symlinks in
post-install - at least that's what i did manually.
to wit:

ln -s /usr/lib/pccts/bin/antlr /usr/bin/antlr
ln -s /usr/lib/pccts/bin/dlg /usr/bin/dlg
ln -s /usr/lib/pccts/bin/genmk /usr/bin/genmk
ln -s /usr/lib/pccts/bin/sor /usr/bin/sor
ln -s /usr/lib/pccts/include /usr/include/pccts

did i miss some point here ?
why _is_ that stuff put into /usr/lib/pccts/*/ ?

ciao
    peter

-----------------------------------------------------------------
peter kadau
email: peter.kadau@web.de
open source is no religion - it just produces the most reliable software
-----------------------------------------------------------------
______________________________________________________________________________
Jetzt und nur hier Ihr original PREMIERE WORLD SportPaket 
plus 100 Euro ExtraPrämie: http://premiere.web.de

Re: [gentoo-dev] pccts lives in /usr/lib/pccts/*/

[Daniel Robbins]

On Tue, Jul 31, 2001 at 06:52:07PM +0200, Peter Kadau wrote:
> hi !
> in trying to get cdrdao cleanly compiled from sources
> (first step to an ebuild hopefully ;-)
> i realized that the binaries and include files of
> pccts live in /usr/lib/pccts/*/
> imho, one should set up appropriate symlinks in
> post-install - at least that's what i did manually.
> to wit:
> 
> ln -s /usr/lib/pccts/bin/antlr /usr/bin/antlr
> ln -s /usr/lib/pccts/bin/dlg /usr/bin/dlg
> ln -s /usr/lib/pccts/bin/genmk /usr/bin/genmk
> ln -s /usr/lib/pccts/bin/sor /usr/bin/sor
> ln -s /usr/lib/pccts/include /usr/include/pccts
> 
> did i miss some point here ?
> why _is_ that stuff put into /usr/lib/pccts/*/ ?

The stuff is in /usr/lib/pccts because the sources are not FHS compliant;
that means that you, as the ebuild creator, are responsible for making sure
that everything gets placed in the correct place and only libraries end up
in /usr/lib.  That way, our ebuild will produce an FHS-compliant install of
cdrdao. 

You can learn more about the FHS at http://www.pathname.com/fhs.  They have
really logical and easy to understand documentation, and I recommend that
anyone who wants to learn more about FHS should go ahead and read it.  Good
stuff.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.