From: Chris Gianelloni <wolf31o2@gentoo.org>
To: "A. Craig West" <acwest-gentoo-dev@craigwest.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE flags
Date: Wed, 22 Oct 2003 20:40:50 -0400 [thread overview]
Message-ID: <1066869650.32010.8.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0310221731230.7253@gizmo.bdkw>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
On Wed, 2003-10-22 at 17:34, A. Craig West wrote:
> So how does one go about getting a USE flag added to an ebuild? In my case, I
> have my own version of the tin ebuild with a 'forgery' USE flag added which
> adds the --enable-forgery option to the .configure command. I'm pretty sure
> I'm not the only person around who uses that option, so it seems like
> something worth contributing to the real ebuild.
I would say you should hack up the ebuild and post a copy of it to
bugzilla as a bug. Assign it to the maintainer of the ebuild and
hopefully they'll accept it. It helps to also have a few people that
you know use it to chime in and also to be around to help the developer
solve any problems there may be with the new functionality, such as
being a testing guinea pig for the developer.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-23 0:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 21:34 [gentoo-dev] USE flags A. Craig West
2003-10-22 22:36 ` Dhruba Bandopadhyay
2003-10-22 22:58 ` david
2003-10-23 0:41 ` Chris Gianelloni
2003-10-23 8:46 ` Spider
2003-10-23 8:49 ` Patrick Kursawe
2003-10-23 9:14 ` Paul de Vrieze
2003-10-23 9:45 ` [gentoo-dev] " Björn Lindström
2003-10-23 11:07 ` Patrick Kursawe
2003-10-23 11:20 ` Björn Lindström
2003-10-23 11:43 ` Patrick Kursawe
2003-10-23 12:35 ` Björn Lindström
2003-10-23 11:39 ` [gentoo-dev] " Philippe Coulonges
2003-10-23 12:20 ` Christian Birchinger
2003-10-23 13:03 ` [gentoo-dev] Gentoo on the ARM Cliff Free
2003-10-23 14:01 ` Mike Frysinger
2003-10-23 15:59 ` [gentoo-dev] USE flags Spider
2003-10-23 21:34 ` [gentoo-dev] " Björn Lindström
2003-10-23 23:08 ` Spider
2003-10-24 15:16 ` Christian Birchinger
2003-10-25 1:41 ` Luke-Jr
2003-10-23 12:25 ` Björn Lindström
2003-10-23 19:27 ` [gentoo-dev] " Masatomo Nakano
2003-10-23 0:40 ` Chris Gianelloni [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 12:38 [gentoo-dev] USE Flags Fabian Zeindl
2005-03-09 13:00 ` Marius Mauch
2005-03-09 13:23 ` Markus Nigbur
2005-03-09 17:13 ` Martin Schlemmer
2005-03-09 17:23 ` Fabian Zeindl
2005-03-09 18:19 ` Benno Schulenberg
2005-03-10 0:56 ` Mike Frysinger
2005-03-10 18:25 ` Benno Schulenberg
2005-03-10 18:37 ` Mike Frysinger
2005-03-10 20:16 ` Drake Wyrm
2005-03-11 1:05 ` Daniel Goller
2005-03-11 1:05 ` Daniel Goller
2005-03-11 19:06 ` Thomas de Grenier de Latour
2005-03-11 19:17 ` Fabian Zeindl
2005-03-20 21:01 ` Paul de Vrieze
2005-03-20 22:21 ` Thomas de Grenier de Latour
2005-03-21 5:11 ` Marius Mauch
2005-03-21 8:56 ` Thomas de Grenier de Latour
2005-03-21 21:55 ` Thomas de Grenier de Latour
2001-09-23 10:38 [gentoo-dev] USE flags Viktor Lakics
2001-09-23 10:50 ` Martin Schlemmer
2001-09-23 12:36 ` Dan Armak
2001-09-23 12:15 ` Karl Trygve Kalleberg
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=1066869650.32010.8.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=acwest-gentoo-dev@craigwest.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