>>>>> On Mon, 22 Aug 2011 20:54:10 +0200, Magnus Fromreide >>>>> <[email protected]> said:
MF> I think feature-remove should It took me a while to get around to following the logic. Fundamentally, if I got it right, you want the default result of the feature_want() to actually not get it. This would be a change to the existing (released) functionality, so I'd argue we can't safely do that. We could offer another flag too though: --enable-minimalist-including-wants or, um, something that would turn on (off!) the functionality you're looking for. MF> wantwantedfeatures is to ignore want's - kind of like remove every MF> feature unless it is necessary. That is a new feature i am proposing. Right, though I'm thinking that default value should be true. My original goal was to simply remove anything "unnecessary". But, admittedly, my definition of "unnecessary" didn't include functionality that was "desired" but could be removed at a cost. -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
