Date: Sun, 01 Mar 2015 13:29:56 -0800 From: Rui Paulo <rpaulo@me.com> To: David Chisnall <theraven@FreeBSD.org> Cc: Harrison Grundy <harrison.grundy@astrodoggroup.com>, freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything Message-ID: <75C49F53-C675-4712-A446-370025EED037@me.com> In-Reply-To: <F1683E9A-6004-4749-BD6E-A5B2472F6C77@FreeBSD.org> References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <CAG=rPVfcB1Fy_8mHq-t5Ay07yrzuSGthQ0ZcGzvp0XG9gSSzkg@mail.gmail.com> <54F35F29.4000603@astrodoggroup.com> <F1683E9A-6004-4749-BD6E-A5B2472F6C77@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 1, 2015, at 11:11, David Chisnall <theraven@FreeBSD.org> wrote: > How would it be in a port? It involves modifying core utilities (some = of which, like ifconfig, rely on kernel APIs that change between = releases) to emit structured output. Maintaining two copies of each = utility, one in the base system with plain-text output only and another = in ports with XML/JSON output would be very painful. It would work fine if we had *libraries* for ifconfig/netstat/route/etc. = Obviously that's not the case and no one has stepped up to implement = them. I've also seen FreeBSD committers expressing their distaste for = libraries for "trivial" command line utilities, which implies they are = unaware of another world beyond the CLI. :-) -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75C49F53-C675-4712-A446-370025EED037>