Hi all,

I've written an ebuild for a math-software called polymake
(www.math.tu-berlin.de/polymake).
You find it attached. You have to digest it yourself to use.
("ebuild polymake-2.3.ebuild digest")
Maybe some people could test it (on amd64 for instance...).

Now some questions:

1.) The Program uses non-autotools "self made" configuration via "make
configure". Currently the Ebuild will ask questions to the user, which I
want to prevent. How can i get around this?
Is there some Bash trick to answer all questions with "Enter" ?
2.) The program needs to be rebuild after an upgrade of dev-lang/perl.
How can i implement this in the ebuild ?
3.) Is there any chance that, after testing, this will land in the
portage tree ? How can I do this,
-email to dev-mailinglist?
-bugzilla ?
- ... ???

thanks
Tom
# Copyright 1999-2008 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

inherit eutils

IUSE="fullconfig"

DESCRIPTION="research tool for polyhedral geometry"
SRC_URI="http://www.math.tu-berlin.de/polymake/download/polymake-2.3.tar.bz2";

HOMEPAGE="http://www.math.tu-berlin.de/polymake";

SLOT="0"
LICENSE="GPL-3"
KEYWORDS="~x86"

DEPEND="dev-libs/gmp
        >=sys-devel/gcc-4.1.2"

src_compile(){
        
        # Interactive Configuration
        if use fullconfig; then 
                emake configure || die "configuration failed"
        fi

        einfo "Due to heavy template usage by the package it requires"
        einfo "up to 300MB of RAM per process. Use MAKEOPTS="-j1" if"
        einfo "you run into trouble."

        if ! use fullconfig; then 
                elog "Polymake will be built with -O3 which is considered safe"
                elog "Set useflag fullconfig to change"
        fi

        emake || die "emake failed"
}

src_install(){
        emake DESTDIR="${D}" install || die "install failed"
}

pkg_postinst(){
        elog "You will need to set up your PATH to use Polymake"
        elog "If you use bash add "
        elog "PATH=\$PATH:/usr/local/polymake/bin;"
        elog "to your .bashrc"
}

Reply via email to