1 |
Ok, thank you very much! |
2 |
|
3 |
Apart from that, I should add those files to the dependencies, right? |
4 |
|
5 |
On Sun, Sep 16, 2012 at 4:33 AM, Michael Orlitzky <michael@××××××××.com>wrote: |
6 |
|
7 |
> On 09/15/2012 11:59 AM, Alexandre Paz Mena wrote: |
8 |
> > |
9 |
> > Thanks, I'll post a bug to upstream. |
10 |
> > |
11 |
> > Meanwhile, instead of adding libs, I worked adding them to econf. |
12 |
> > |
13 |
> > But a new problem has appeared, mldonkey-3.1.3 seems to not have a |
14 |
> > init.d script. I thought that was the ebuild work, but both ebuilds are |
15 |
> > almost the same and now I'm looking through the tarballs to see any |
16 |
> > differences related to that. |
17 |
> |
18 |
> The init scripts are usually stored in the package's "files" directory. |
19 |
> You should see the mldonkey one here: |
20 |
> |
21 |
> $ ls /usr/portage/net-p2p/mldonkey/files/ |
22 |
> total 12K |
23 |
> -rw-r--r-- 1 root root 1.6K 2008-06-30 12:12 2.9.5-execstacks.patch |
24 |
> -rw-r--r-- 1 root root 887 2007-01-24 12:40 mldonkey.confd-2.8 |
25 |
> -rw-r--r-- 1 root root 3.1K 2011-10-23 14:22 mldonkey.initd |
26 |
> |
27 |
> The ebuild in portage (tries to) install this: |
28 |
> |
29 |
> ... |
30 |
> newinitd "${FILESDIR}/mldonkey.initd" mldonkey |
31 |
> |
32 |
> |
33 |
> A guess: you copied the ebuilds to an overlay, but didn't copy the |
34 |
> "files" directory. Normally you'd get an error as a result, but there's |
35 |
> a bug (lots of them, actually) in the ebuild. In earlier EAPIs, the |
36 |
> dofoo/newfoo functions could fail but would not do so automatically. The |
37 |
> usual way to handle this is with e.g. |
38 |
> |
39 |
> newinitd x y || die "newinitd didn't work" |
40 |
> |
41 |
> The ebuild doesn't do this, so it happily continues after failing to |
42 |
> install the init script. |
43 |
> |
44 |
> |
45 |
|
46 |
|
47 |
-- |
48 |
Alexandre Paz Mena |