public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE & Portages
Date: Mon Jan 15 13:05:01 2001	[thread overview]
Message-ID: <3A635161.117B0150@gottinger.de> (raw)
In-Reply-To: 20010115130346.A2078@kabbu.akopia.com

"Jerry A!" wrote:

> On Mon, Jan 15, 2001 at 09:29:48AM -0700, drobbins@gentoo.org wrote:
> : On Mon, Jan 15, 2001 at 03:32:16AM -0500, Jerry A! wrote:
> :
> : > So, I was thinking (yeah, I know how dangerous that is).  Is it possible
> : > to specify USE on the command-line?  If not, how out-of-place would it
> : > be to specify USE in the .ebuild?
> :
> : Right now, you can't specify USE as an environment variable, it's not really
> : intended for that purpose.  You're supposed to use it to tell Portage to
> : enable or disable certain optional functionality on a system-wide basis, so that
> : the ebuilds know whether or not to compile-in optional GNOME support if it
> : is available, for instance.
> :
> : Maybe if you can describe the specific problem you're trying to solve, we
> : can help you find a better solution (or create a solution if needed).
>
> What I'm looking for is optional functionality of a portage-specific
> basis.
>
> For instance, instead of having exim, exim-ldap, postfix, postfix-tls,
> etc... ebuilds which may or may not get out of sync (like the qmail ones
> currently are), I'd like to have one portage.  In that portage or
> through the use of a command-line variable have the user choose what
> options they want (tls, mysql, ldap, etc...).  Or, at the very least
> have a USE= line in the ebuild that they can edit to suit their tastes.
>
> If this isn't possible, then I suggest adding options like: mta-tls,
> mta-mysql, mta-ldap, etc... to /etc/make.defaults and /etc/make.conf.

I think that is a good idea, but don't use only mysql or ldap because I'm
planning to use that for stuff like gnome-db, php

THX achim

>
>
> My only reservation for this is that we may eventually run into MTAs
> that don't support all the functionality.  But then again, that can be
> solved, so maybe I'm making a mountain out of a molehill.

>
>
> Anyway, let me know how you'd like me to proceed.
>
>         --Jerry
>
> name:  Jerry Alexandratos         ||  Open-Source software isn't a
> phone: 703.599.6023               ||  matter of life or death...
> email: jerry@akopia.com           ||  ...It's much more important
>                                   ||  than that!
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev



  reply	other threads:[~2001-01-15 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-15  1:34 [gentoo-dev] USE & Portages Jerry A!
2001-01-15  9:30 ` drobbins
2001-01-15 11:06   ` Jerry A!
2001-01-15 13:05     ` Achim Gottinger [this message]
2001-01-15 13:09       ` Jerry A!
2001-01-15 13:32         ` Achim Gottinger
2001-01-15 13:55           ` Jerry A!
2001-01-15 14:42             ` Achim Gottinger
2001-01-16 10:17             ` Achim Gottinger

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=3A635161.117B0150@gottinger.de \
    --to=320095285153-0001@t-online.de \
    --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