Re: [GNU Crypto] Proposal for a small build-system change

[Casey Marshall]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jun 16, 2003 at 07:39:56PM +1000, Raif S. Naffah wrote:

> [...]
>
> i'm interested in hearing Casey's opinion too, since he'll be confronted 
> (may be) with a similar situation for Gentoo.
> 

Gentoo makes packaging almost absurdly easy. Here is my current
incarnation of gnu-crypto-2.0.0.ebuild:

8< -----
DESCRIPTION="GNU cryptography package for Java"
HOMEPAGE="http://www.gnu.org/software/gnu-crypto/";
SRC_URI="ftp://ftp.gnupg.org/gcrypt/gnu-crypto/gnu-crypto-${PV}.tar.gz";
MY_P="gnu-crypto-${PV}"
S=${WORKDIR}/${MY_P}
LICENSE="GPL-2"
SLOT="1"
KEYWORDS="~x86"
DEPEND=">=virtual/jdk-1.2"

src_unpack() {
        unpack ${MY_P}.tar.gz
}

src_compile() {
        cd ${S}
        local myconf
        myconf="--with-javac"
        use jikes && myconf="--with-jikes"
        econf ${myconf} || die "Configure failed."
        emake || die "Compilation failed."
}

src_install() {
        dojar source/gnu-crypto.jar
        if [ -e jce/javax-crypto.jar ]; then
                dojar jce/javax-crypto.jar
        fi
        if [ -e security/javax-security.jar ]; then
                dojar security/javax-security.jar
        fi
        doinfo docs/manual/gnu-crypto*.info
}
8< -----

This only builds the JARs for "traditional" Java SDKs, but I don't
expect the GCJ ebuild to be that much more difficult.

The only problem seems to be that the JCE and javax.security bits are
compiled by default, even if the user has a 1.4 JDK.

- -- 
Casey Marshall || address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+7nwMgAuWMgRGsWsRAkrqAJ9DfER6wqLSh3rQ7oO12nsCf8pzwQCfdnoe
E2BK4PfSiSASnnsOZwX33eQ=
=/753
-----END PGP SIGNATURE-----