public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [rfc] making autotools.eclass depends flexible
Date: Sat, 06 Mar 2010 09:11:15 +0200	[thread overview]
Message-ID: <4B920013.7070002@gentoo.org> (raw)
In-Reply-To: <201003051359.58724.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

On 03/05/2010 08:59 PM, Mike Frysinger wrote:
> sometimes i have optional patches (ignoring the "patches should always be
> applied") where autotools should be run.  always inheriting autotools is
> currently annoying because it always adds the related dependencies.  USE based
> inherits are obviously out.
> 
> so unless there's some burgeoning standard i'm not aware of, below is what i
> have in mind.  packages set AUTOTOOLS_AUTO_DEPEND to "no" before inheriting
> autotools.eclass and that allows them to put ${AUTOTOOLS_DEPEND} behind a USE
> flag in their own DEPEND string.
> 

What we use in Java is JAVA_PKG_OPT_USE to declare what use flag the
DEPENDs should be under. This approach doesn't allow the ebuild
maintainer to forget adding the depends.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2010-03-06  7:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 18:59 [gentoo-dev] [rfc] making autotools.eclass depends flexible Mike Frysinger
2010-03-06  7:11 ` Petteri Räty [this message]
2010-03-06 18:28   ` [gentoo-dev] " Jonathan Callen
2010-03-06 18:45     ` Petteri Räty
2010-03-07 17:42   ` [gentoo-dev] " Mike Frysinger
2010-03-07 18:31     ` Petteri Räty
2010-03-07 18:36       ` Mike Frysinger
2010-03-07 19:08         ` Petteri Räty
2010-03-07 21:44           ` Mike Frysinger
2010-03-08  5:37             ` Petteri Räty

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=4B920013.7070002@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-dev@lists.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