[gentoo-dev] ebuild help

[gentoo-dev] ebuild help

[Brett]

Greetings,
I have a few Linux programs which I would like to use, but which are not
in portage. I have attempted to make some ebuild scripts (via the ebuild
HOWTO) for these  programs, but I can't get them to work.

The error I receive is:
{
# emerge /usr/local/portage/app-office/bhpos-base/app-office/bhpos-base
Calculating dependencies
emerge: there are no masked or unmasked ebuilds to satisfy
"/usr/local/portage/app-office/bhpos-base/app-office/bhpos-base".
                                                                                
!!! Error calculating dependencies. Please correct.

}//end error

I have tried everything I can think of, including commenting out all the
required dependencies.

I have also set:
PORTDIR_OVERLAY="/usr/local/portage"

Any help is appreciated :-)
Brett

The ebuild script:
{
cat bhpos-base-1.0.1-1_rc1.ebuild
# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: $
 
DESCRIPTION="Bananahead Point-of-sale software"
HOMEPAGE="http://www.bananapos.com/"
SRC_URI="http://bananapos.com/download/bhpos/stable/base/${P}.tar.gz"
LICENSE="GPL2"
SLOT="0"
KEYWORDS="~x86"
 
IUSE="X gnome"
DEPEND=">=autoconf-2.54
        >=automake-1.73
        >=libtool-1.4.3-r1
        >=make-3.8.0
        >=gettext-0.11.5
        >=intltools-0.23
        >=pkgconfig-0.15.0"
 
RDEPEND=""
S=${WORKDIR}/${P}
 
src_unpack() {
        unpack ${A} || die
}
 
src_compile() {
                ./configure \
                --host=${CHOST} \
                --prefix=/usr \
                --infodir=/usr/share/info \
                --mandir=/usr/share/man || die "./configure failed"
}
 
src_install() {
        make \
                prefix=${D}/usr \
                mandir=${D}/usr/share/man \
                infodir=${D}/usr/share/info \
                install || die
}

}//end ebuild script


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] ebuild help

[Mike Frysinger]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1022 bytes --]

On Tuesday 23 September 2003 21:17, Brett wrote:
> Greetings,
> I have a few Linux programs which I would like to use, but which are not
> in portage. I have attempted to make some ebuild scripts (via the ebuild
> HOWTO) for these  programs, but I can't get them to work.
>
> The error I receive is:
> {
> # emerge /usr/local/portage/app-office/bhpos-base/app-office/bhpos-base
> Calculating dependencies
> emerge: there are no masked or unmasked ebuilds to satisfy
> "/usr/local/portage/app-office/bhpos-base/app-office/bhpos-base".
>
> !!! Error calculating dependencies. Please correct.
>
> }//end error
>
> I have tried everything I can think of, including commenting out all the
> required dependencies.

you're doing it wrong ...
the PORTDIR_OVERLAY is just like the official portdir.  that said, you should 
have the ebuild here:
/usr/local/portage/app-office/bhpos-base/bhpos-base-1.20.ebuild
(note the 1.20 is a version i just made up :P)
then you can just do `emerge bhpos-base`
-mike

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

Re: [gentoo-dev] ebuild help

[Brian Jackson]

On Tuesday 23 September 2003 08:17 pm, Brett wrote:
> Greetings,
> I have a few Linux programs which I would like to use, but which are not
> in portage. I have attempted to make some ebuild scripts (via the ebuild
> HOWTO) for these  programs, but I can't get them to work.
>
> The error I receive is:
> {
> # emerge /usr/local/portage/app-office/bhpos-base/app-office/bhpos-base

did you try "emerge bhpos-base"

the ebuild should be:
/usr/local/portage/app-office/bhpos-base/bhpos-base-1.0.1-1_rc1.ebuild

> Calculating dependencies
> emerge: there are no masked or unmasked ebuilds to satisfy
> "/usr/local/portage/app-office/bhpos-base/app-office/bhpos-base".
>
> !!! Error calculating dependencies. Please correct.
>
> }//end error
>
> I have tried everything I can think of, including commenting out all the
> required dependencies.
>
> I have also set:
> PORTDIR_OVERLAY="/usr/local/portage"
>
> Any help is appreciated :-)
> Brett
>
> The ebuild script:
> {
> cat bhpos-base-1.0.1-1_rc1.ebuild
<snip>

-- 
Home -- http://www.brianandsara.net
Gentoo -- http://gentoo.brianandsara.net
OpenGFS -- http://opengfs.sourceforge.net


--
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Ebuild Help...

[Matthew Walker]

I'm writing my first ebuild, and I'm having a hard time figuring out how
to get it to install all the files properly once they've been created in
the image directory. I've included my ebuild file. Any help would be
greatly appreciated.
# Copyright 1999-2000 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# Author Matthew Walker <mwalker@kydance.net>

S=${WORKDIR}/${PN}-${PV}
DESCRIPTION="Xscorch is a clone of the classic DOS game, 'Scorched Earth'."
SRC_URI="http://chaos2.org/xscorch/${PN}-${PV}.tar.gz
         http://utoxin.kydance.net/xscorch/${PN}-${PV}.tar.gz"

HOMEPAGE="http://chaos2.org/xscorch/"
SLOT="0"
LICENSE="GPL"
DEPEND=">=x11-libs/gtk-1.2"

src_unpack() {
    unpack ${PN}-${PV}.tar.gz
    cd ${S}
}

src_compile() {
    ./configure --prefix=/usr --bindir=/usr/bin --datadir=/usr/share
    --mandir=/usr/share/man --enable-opt --host=${CHOST} || die    emake || die
}

src_install () {
    make DESTDIR=${D} install || die

    dodir /usr/bin
    dodir /usr/share/doc/${PN}-${PV}
    dodir /usr/share/${PN}
    dodir /usr/share/${PN}/images
    dodir /usr/share/${PN}/sounds

    dobin ${D}/usr/bin/xscorch
    dobin ${D}/usr/bin/xscorch-server

    insinto /usr/share/man/man6
    doins ${D}/usr/share/man/man6/${PN}.6.gz

    dodoc AUTHORS ChangeLog COPYING INSTALL NEWS README TODO
}

Re: [gentoo-dev] Ebuild Help...

[Markus Brischke]

Quoting Matthew Walker (mwalker@kydance.net):
> I'm writing my first ebuild, and I'm having a hard time figuring out how
> to get it to install all the files properly once they've been created in
> the image directory. I've included my ebuild file. Any help would be
> greatly appreciated.
...
> src_install () {
>     make DESTDIR=${D} install || die
> 
>     dodir /usr/bin
>     dodir /usr/share/doc/${PN}-${PV}
>     dodir /usr/share/${PN}
>     dodir /usr/share/${PN}/images
>     dodir /usr/share/${PN}/sounds
> 
>     dobin ${D}/usr/bin/xscorch
>     dobin ${D}/usr/bin/xscorch-server
> 
>     insinto /usr/share/man/man6
>     doins ${D}/usr/share/man/man6/${PN}.6.gz
> 
>     dodoc AUTHORS ChangeLog COPYING INSTALL NEWS README TODO
> }

Hi, i have written yesterday my first too ;) If i read all the stuff
right the ${D} in the do<something> helperapps is unnecessary. This is
hardly ;) explained in the table in http://www.gentoo.org/doc/gentoo-howto.html
I read many of the ebuildfiles to get here and there a picture :) There
is a usefull manpage (man 5 ebuild) and a usefull skeleton and last but
not least the documentation and mailinglistarchive (is there a search
mechanism anywhere?).

If you are not sure if your installscript puts the thing into right
directories (meaning outside PORTAGE_TMPDIR) then use
FEATURES="sandbox". If i have read right this will protect you from
overwriting you system :) But (!) watch carefully imho not everything is
logged. e.g. the bernstein setup mechanism fails using mkdir(), but
there is no logwarning because no "new" file|dir created.

Another thing is the way how to install things. Imho it is a better
style to patch the Makefiles(.in) to improve or correct the ${D}
installation than to dodir/dobin/insinto,... doing yourself. The reason
for this the potential difference between a "make install" and doing the
"same" yourself. I found it maddening in some distros that the
packagemaintainers forgot these and that in the package that a "make
install" would have installed. Another adavantage would be if the author
of the package change the installation your patch won't properly apply
(in most cases not in all!). The Request for controlling the makefiles
is so right, but in these concepts even the controller make mistakes and
every hinting mechanism like sandox and (failed) patching should be used
but must not be relied on.

I hope this will help you and that i don't say anything wrong :)

Markus Brischke aka Zoke