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