1 |
On Tue, Jul 31, 2001 at 06:52:07PM +0200, Peter Kadau wrote: |
2 |
> hi ! |
3 |
> in trying to get cdrdao cleanly compiled from sources |
4 |
> (first step to an ebuild hopefully ;-) |
5 |
> i realized that the binaries and include files of |
6 |
> pccts live in /usr/lib/pccts/*/ |
7 |
> imho, one should set up appropriate symlinks in |
8 |
> post-install - at least that's what i did manually. |
9 |
> to wit: |
10 |
> |
11 |
> ln -s /usr/lib/pccts/bin/antlr /usr/bin/antlr |
12 |
> ln -s /usr/lib/pccts/bin/dlg /usr/bin/dlg |
13 |
> ln -s /usr/lib/pccts/bin/genmk /usr/bin/genmk |
14 |
> ln -s /usr/lib/pccts/bin/sor /usr/bin/sor |
15 |
> ln -s /usr/lib/pccts/include /usr/include/pccts |
16 |
> |
17 |
> did i miss some point here ? |
18 |
> why _is_ that stuff put into /usr/lib/pccts/*/ ? |
19 |
|
20 |
The stuff is in /usr/lib/pccts because the sources are not FHS compliant; |
21 |
that means that you, as the ebuild creator, are responsible for making sure |
22 |
that everything gets placed in the correct place and only libraries end up |
23 |
in /usr/lib. That way, our ebuild will produce an FHS-compliant install of |
24 |
cdrdao. |
25 |
|
26 |
You can learn more about the FHS at http://www.pathname.com/fhs. They have |
27 |
really logical and easy to understand documentation, and I recommend that |
28 |
anyone who wants to learn more about FHS should go ahead and read it. Good |
29 |
stuff. |
30 |
|
31 |
Best Regards, |
32 |
|
33 |
-- |
34 |
Daniel Robbins <drobbins@g.o> |
35 |
Chief Architect/President http://www.gentoo.org |
36 |
Gentoo Technologies, Inc. |