ebuild help for logdog.pl

Message

sirsycho · Post by **sirsycho** » Sun Sep 04, 2005 2:58 pm

Hello,

I am a newbie to ebuild building and have been trying to get this perl script installed via ebuild. I have searched the forums and tried the stuff I've found (in addition to the official ebuild howto). I have a feeling this might be a problem related to the Makefile in the download package, is there a way to work around that until I can contact the developer or am I completely wrong.

My ebuild and errors...

Code: Select all

DESCRIPTION=" A daemon for monitoring syslogd messages and alerting administrators"

HOMEPAGE="http://caspian.dotconf.net/menu/Software/LogDog/"

SRC_URI="http://caspian.dotconf.net/menu/Software/LogDog/${PN}-v${PV}-RC5.tar.gz"

LICENSE="as-is"

SLOT="0"

KEYWORDS="x86"

IUSE=""

DEPEND=""

RDEPEND="dev-lang/perl"

S=${WORKDIR}/${PN}-v${PV}-RC5

src_unpack() {
        unpack ${A}
        cd ${WORKDIR}/logdog-v2.00-RC5
}


src_install() {
        make install  || die
}

ERROR:

Code: Select all

 
# ebuild /usr/local/portage/app-admin/logdog/logdog-2.00.ebuild install
>>> Downloading http://gentoo.netnitco.net/distfiles/logdog-v2.00-RC5.tar.gz
--09:46:03--  http://gentoo.netnitco.net/distfiles/logdog-v2.00-RC5.tar.gz
           => `/usr/portage/distfiles/logdog-v2.00-RC5.tar.gz'
Resolving gentoo.netnitco.net... 216.176.132.235
Connecting to gentoo.netnitco.net[216.176.132.235]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
09:46:03 ERROR 404: Not Found.

>>> Downloading http://caspian.dotconf.net/menu/Software/LogDog/logdog-v2.00-RC5.tar.gz
--09:46:03--  http://caspian.dotconf.net/menu/Software/LogDog/logdog-v2.00-RC5.tar.gz
           => `/usr/portage/distfiles/logdog-v2.00-RC5.tar.gz'
Resolving caspian.dotconf.net... 69.20.172.62
Connecting to caspian.dotconf.net[69.20.172.62]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15,039 [application/x-tar]

100%[====================================================================================================================>] 15,039        48.97K/s

09:46:03 (48.82 KB/s) - `/usr/portage/distfiles/logdog-v2.00-RC5.tar.gz' saved [15,039/15,039]

>>> md5 files   ;-) logdog-2.00.ebuild
>>> md5 files   ;-) files/digest-logdog-2.00
>>> md5 src_uri ;-) logdog-v2.00-RC5.tar.gz
>>> Unpacking source...
>>> Unpacking logdog-v2.00-RC5.tar.gz to /var/tmp/portage/logdog-2.00/work
>>> Source unpacked.
Installing LogDog...
      install   logdog.pl       /usr/local/sbin
ACCESS DENIED  open_wr:   /usr/local/sbin/logdog.pl
install: cannot create regular file `/usr/local/sbin/logdog.pl': Permission denied
make: *** [default] Error 1

!!! ERROR: app-admin/logdog-2.00 failed.
!!! Function src_compile, Line 556, Exitcode 2
!!! emake failed
!!! If you need support, post the topmost build error, NOT this status message.

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/var/log/sandbox/sandbox-app-admin_-_logdog-2.00-21854.log"

open_wr:   /usr/local/sbin/logdog.pl
--------------------------------------------------------------------------------

Thanks in advance...

commonloon · Post by **commonloon** » Mon Sep 05, 2005 1:53 am

A couple of sanity check questions:

1. Are you root?

2. Does /usr/local/{sbin,bin} exist?

sirsycho · Post by **sirsycho** » Mon Sep 05, 2005 1:27 pm

1. Are you root?

Yes, I am.

2. Does /usr/local/{sbin,bin} exist?

Yes both exist.

Thanks again...

xoomix · Post by **xoomix** » Fri Sep 09, 2005 12:37 pm

elmicha · Post by **elmicha** » Fri Sep 09, 2005 3:09 pm

An ebuild (even if it is your own) should not write into /usr/local. Change the ebuild so that it puts the binaries into /usr/bin or /usr/sbin. If the Makefile doesn't have parameters that you can change when calling make, have the ebuild use sed to change the Makefile.

commonloon · Post by **commonloon** » Sun Sep 11, 2005 1:07 pm

What does the makefile look like? Have you checked out:

http://www.gentoo.org/proj/en/devrel/ha ... #doc_chap3

... D,S,src_install, install vs einstall

ps: not necessarily bad to install to /usr/local if its a "Local" package (http://www.pathname.com/fhs/). Of course, there are complications in that $PATH for example may not contain it.