| 1 |
On Tue, 5 Jan 2010 12:17:39 +0100, Christian Faulhammer |
| 2 |
<fauli@g.o> wrote: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> "Alex Legler (a3li)" <a3li@g.o>: |
| 7 |
> > a3li 10/01/05 10:30:43 |
| 8 |
> > |
| 9 |
> > Modified: metadata.xml ChangeLog |
| 10 |
> > Added: bip-0.8.4.ebuild |
| 11 |
> > Removed: bip-0.8.1.ebuild |
| 12 |
> > Log: |
| 13 |
> > Version bump, add 'noctcp' option to disable automatic CTCP |
| 14 |
> > VERSION replies. Remove old version (Portage version: |
| 15 |
> > 2.2_rc59/cvs/Linux x86_64) |
| 16 |
> |
| 17 |
> [...] |
| 18 |
> |
| 19 |
> > IUSE="debug noctcp ssl vim-syntax oidentd" |
| 20 |
> |
| 21 |
> Please avoid no* USE flags, they are bad behaviour and will earn you |
| 22 |
> a spanking. Use USE flag defaults if you want to activate it by |
| 23 |
> default. |
| 24 |
> |
| 25 |
|
| 26 |
I don't think the implications regarding noblah USE flags as stated in |
| 27 |
the devmanual apply to this case. There is no change in dependencies |
| 28 |
with that flag, so no problem for any arch teams. |
| 29 |
|
| 30 |
Also, I like the semantics of noctcp better. It's not just about |
| 31 |
enabling or disabling the CTCP stuff for flexibility's sake, it's about |
| 32 |
*specifically disabling* it avoid getting hit by morons sending |
| 33 |
floodbots to Freenode (or $any_irc_network). |
| 34 |
|
| 35 |
-- |
| 36 |
Alex Legler | Gentoo Security / Ruby |
| 37 |
a3li@g.o | a3li@××××××××××.de |
Archives