Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Mar 2015 01:16:50 -0800
From:      Julian Elischer <julian@freebsd.org>
To:        Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: Massive libxo-zation that breaks everything
Message-ID:  <54F42A82.1020308@freebsd.org>
In-Reply-To: <54F36431.30506@freebsd.org>
References:  <54F31510.7050607@hot.ee>	<54F34B6E.2040809@astrodoggroup.com> <CAG=rPVfcB1Fy_8mHq-t5Ay07yrzuSGthQ0ZcGzvp0XG9gSSzkg@mail.gmail.com> <54F35F29.4000603@astrodoggroup.com> <54F36431.30506@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 3/1/15 11:10 AM, Allan Jude wrote:
> On 2015-03-01 13:49, Harrison Grundy wrote:
>> Thanks!
>>
>> That does seem useful, but I'm not sure I see the reasoning behind
>> putting into base, over a port or package, since processing XML in base
>> is a pain, and it can't serve up JSON or HTML without additional
>> utilities anyway.
>>
>> (If I'm reviving a long-settled thing, let me know and I'll drop it. I'm
>> trying to understand the use case for this.)
>>
>> --- Harrison
>>
>> On 03/01/15 10:31, Craig Rodrigues wrote:
>>> On Sun, Mar 1, 2015 at 9:25 AM, Harrison Grundy <
>>> harrison.grundy@astrodoggroup.com> wrote:
>>>
>>>>
>>>> If someone could summarize what this is, I'd greatly appreciate it.
>>>>
>>> https://lists.freebsd.org/pipermail/freebsd-arch/2014-July/015633.html
>>> _______________________________________________
>>> freebsd-current@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>>
> I think you're missing the important bit here.
>
> This isn't about adding a parser for anything, this is about making the
> tools in base, like netstat, wc, uptime, etc, output in JSON or XML, so
> you can use the data programmatically.
exactly. I think that's the wrong path to take.
we have to change EVERY PROGRAM IN THE WORLD.
if we develop a suitable post processor with pluggable grammars, we 
save a lot of work.
given enough examples you could almost have automatically generated 
grammars.


>
> Your scripts no longer have to rely on awk/sed/grep magic to get a
> specific bit of information out of the uptime command, the command can
> just output the data in a structured machine readable format.
>
> I am not sure how you can put netstat into the ports tree.
>
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F42A82.1020308>