public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bob Phan <bob@endlessrecursion.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild optional dependancy question
Date: Mon, 11 Mar 2002 15:24:19 +0000 (/etc/localtime)	[thread overview]
Message-ID: <Pine.LNX.4.21.0203111512000.6352-100000@lucifer.evil-core.com> (raw)
In-Reply-To: <20020311152003.A1A4E33E7A@bmr.zenmonkey.org>

On Mon, 11 Mar 2002, Brian M. Rzycki wrote:

> The second program (yafc -- yafc.sourceforge.net) is not as
> straightforward as zile.  For the uninitiated, yafc is an interactive
> ftp client similar to lftp with support for socks4/5, kerberos4/5, and
> sftp.  Yafc's configure script automatically enables/disables ssh and
> readline if it finds the libraries.  The same is not true for socks and
> kerberos.  I merged kth-krb (kerberos4) and saw it installed everything in
> /usr/athena.  When I manually gave configure the parameter
> --with-krb4=/usr/athena it compiled with kerberos4 support.  I had similar
> results with dante (socks4/5).  
> 
> After discovering I had to manually apply parameters to the configure
> script in order for socks/kerberos support I went looking for use
> variables. I planned on using the "if [ -z "use_var" ]" trick from the
> gentoo-howto.  Unfortunately I didn't see either socks or krb4/5 use
> variables.  
> 
> So my question is this:  What is the correct gentoo way of discovering
> these packages?  Should I consult /var/db/pkg/app_group/app_name* to see
> if the program is installed?  Should I check the physical location for
> the libraries (a la -d /usr/athena)?  Or am I just a numbskull and
> missing some obvious feature of portage which makes my life much easier?

I was actually planning on making a yafc ebuild myself :).  Anyway, you
want to use the notation like this (which is all in the developer howto):

DEPEND="...
        lots of usual stuff
        ...
        NAME_OF_USE_VAR? ( >=category/package-version_number )

for example:

        krb4? ( >=app-crypt/kth-krb-1.1-r1 )
 
Then, in the src_compile secion of the ebuild, you want to put:

local myopts

if [ -n "`use krb4`" ]
then
        myopts="${myopts} --with-krb4"
fi

./configure \
        ${myopts}

You might want to read some other ebuilds to get a good feel as to how
this works.

Disclaimer:
I'm not a gentoo developer, so my suggestions are subject to critisizm.
Also, krb4 is not a recognized USE parameter.  You might want to ask an
official gentoo developer how that should be handled, perhaps there should
be an official gentoo USE parameter for kerberos 4 and 5.  My suggestion
is krb4 and krb5, but that's just my suggestion.

Hope this was helpful.

-- 
/*
 * Bob Phan <bob@endlressrecursion.net,rphan@nrgn.com>
 * Computational Chemistry Informatics
 * Neurogen Corporation
 * (203)488-8201 x4645
 *
 * To understand recursion, you must first understand recursion.
 */



      reply	other threads:[~2002-03-11 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 15:20 [gentoo-dev] ebuild optional dependancy question Brian M. Rzycki
2002-03-11 15:24 ` Bob Phan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.21.0203111512000.6352-100000@lucifer.evil-core.com \
    --to=bob@endlessrecursion.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox