On 08/27/2012 01:42 AM, David Seikel wrote: > On Sun, 26 Aug 2012 21:34:17 -0500 Rob Landley <[email protected]> wrote: > >> I think the best way to do it is to make the basic implementation be >> "the non-stupid bits of posix", and then an additional config symbol >> should go beyond posix where applicable. (Or fill in the actively >> stupid bits, like the full horror of xargs whitespace parsing which I >> still haven't implemented yet both because it's kind of horrible and >> because -0 renders it obsolete, but Rich Felker wants it, so it's on >> my todo list.) > > So these would be generic compile time config options for all of > toybox? Plain, sane, or insane respectively?
I was thinking attached to the specific commands, of which there are currently something like 3 that would care. I could put a "PEDANTIC" config option in the general menu, but the problem is allyesconfig/allnoconfig. Adding an option that _disables_ functionality is backwards, and makes allyesconfig funky. But having an option required for some functionality be separated way away from that functionality is also funky. Then again, TOYBOX_FLOAT is already doing that... (There's also the fact it only really applies to posix. I don't care much about following LSB closely since it's such a terrible standard, and the android and other stuff doesn't really have a standard.) Rob -- GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code. Either it's "mere aggregation", or a license violation. Pick one. _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
