1 |
Just a quick thought: |
2 |
when you do make install do you do: |
3 |
make DESTDIR=${D} install || die |
4 |
|
5 |
or: |
6 |
make \ |
7 |
prefix=${D}/usr \ |
8 |
mandir=${D}/usr/share/man \ |
9 |
infodir=${D}/usr/share/info \ |
10 |
install || die |
11 |
|
12 |
With the first one I am getting sandbox violation for many "not completely |
13 |
compliant" packages. Second one worked nicely so far. Even if some stuff goes |
14 |
(for example ) to /usr/doc instead of /usr/share/doc but it at least goes |
15 |
under ${D} and can be fixed later-on. |
16 |
|
17 |
George |
18 |
|
19 |
|
20 |
On Saturday 13 April 2002 11:43, Terje Kvernes wrote: |
21 |
> Terje Kvernes <terjekv@××××××××.no>: |
22 |
> > now, fixing "easysock", "ggz-client-libs" and "ggz-gtk-client" is |
23 |
> > trivial. but, "ggz-client-libs" installs /usr/bin/ggz-config, which |
24 |
> > the "ggz-gtk-games" configure file uses to find ggzs data- and |
25 |
> > lib-dir. this might be all well, if it hadn't been for the sandbox, |
26 |
> > which cries "yelp" and dies. for obvious reasons. now, what to do? |
27 |
> |
28 |
> Spider <spider@g.o> writes: |
29 |
> > the sandbox will only yell yelp and die if the program attempts to |
30 |
> > -write- to the disk.. why does the configure script attempt to do |
31 |
> > that? Find that reason and you have your solution nearby. |
32 |
> |
33 |
> sorry, I should have been more spesific. when /usr/bin/ggz-config |
34 |
> returns that '/usr/share/ggz' is the datadirectory, 'make install' |
35 |
> will attempt to create this directory. |
36 |
> |
37 |
> ggz-config is called during configure, and this is when this path is |
38 |
> set. :/ |