Hi,

"Alex Legler (a3li)" <a3li@gentoo.org>:
> a3li 10/01/05 10:30:43
>
> Modified: metadata.xml ChangeLog
> Added: bip-0.8.4.ebuild
> Removed: bip-0.8.1.ebuild
> Log:
> Version bump, add 'noctcp' option to disable automatic CTCP VERSION
> replies. Remove old version (Portage version: 2.2_rc59/cvs/Linux
> x86_64)

[...]

> IUSE="debug noctcp ssl vim-syntax oidentd"

Please avoid no* USE flags, they are bad behaviour and will earn you a
spanking. Use USE flag defaults if you want to activate it by default.

V-Li

--
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>

On Tue, 5 Jan 2010 12:17:39 +0100, Christian Faulhammer
<fauli@gentoo.org> wrote:

> Hi,
>
> "Alex Legler (a3li)" <a3li@gentoo.org>:
> > a3li 10/01/05 10:30:43
> >
> > Modified: metadata.xml ChangeLog
> > Added: bip-0.8.4.ebuild
> > Removed: bip-0.8.1.ebuild
> > Log:
> > Version bump, add 'noctcp' option to disable automatic CTCP
> > VERSION replies. Remove old version (Portage version:
> > 2.2_rc59/cvs/Linux x86_64)
>
> [...]
>
> > IUSE="debug noctcp ssl vim-syntax oidentd"
>
> Please avoid no* USE flags, they are bad behaviour and will earn you
> a spanking. Use USE flag defaults if you want to activate it by
> default.
>

I don't think the implications regarding noblah USE flags as stated in
the devmanual apply to this case. There is no change in dependencies
with that flag, so no problem for any arch teams.

Also, I like the semantics of noctcp better. It's not just about
enabling or disabling the CTCP stuff for flexibility's sake, it's about
*specifically disabling* it avoid getting hit by morons sending
floodbots to Freenode (or $any_irc_network).

--
Alex Legler | Gentoo Security / Ruby
a3li@gentoo.org | a3li@jabber.ccc.de