From owner-freebsd-current@FreeBSD.ORG Mon Mar 2 09:16:57 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4072B7CC; Mon, 2 Mar 2015 09:16:57 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E967F5EE; Mon, 2 Mar 2015 09:16:56 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t229Gt0G003317 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Mar 2015 01:16:55 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54F42A82.1020308@freebsd.org> Date: Mon, 02 Mar 2015 01:16:50 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Allan Jude , freebsd-current@freebsd.org Subject: Re: Massive libxo-zation that breaks everything References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <54F35F29.4000603@astrodoggroup.com> <54F36431.30506@freebsd.org> In-Reply-To: <54F36431.30506@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2015 09:16:57 -0000 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. > >