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