Massive libxo-zation that breaks everything
bright at mu.org
Mon Mar 2 13:23:35 UTC 2015
On 3/2/15 4:14 AM, Julian Elischer wrote:
> On 3/1/15 10:49 AM, Harrison Grundy wrote:
>> 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.)
> To me it would almost seem more useful to have a programmable filter
> for which you could produce
> parse grammars to parse the output of various programs..
> ifconfig -a | xmlize -g ifconfig | your-favourite-xml-parser
> with a set of grammars in /usr/share/xmlize/
> then we could use it for out-of-tree programs as well if we wrote
> grammars for them..
> The sentiment of machine-readable output is nice, but I think it's
> slightly off target.
> we shouldn't have to change all out utilities, and it isn't going to
> help at all with 3rd party apps,
> e.g. samba stuff. A generally easy to program output grammar parser
> would be truely useful.
> and not just for FreeBSD.
> I've been watching with an uncomfortable feeling, but it's taken me a
> while to put my
> finger on what it was..
Are you sure it's not the hairs on the back of your neck standing up due
Juniper has been doing this for years and it's very useful for them.
More information about the freebsd-current