From owner-freebsd-hackers@freebsd.org Fri Dec 15 08:26:53 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00CECE9F413 for ; Fri, 15 Dec 2017 08:26:53 +0000 (UTC) (envelope-from maxim.konovalov@gmail.com) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 830326CBBB for ; Fri, 15 Dec 2017 08:26:52 +0000 (UTC) (envelope-from maxim.konovalov@gmail.com) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.15.2/8.15.2) with ESMTP id vBF8QigI033382; Fri, 15 Dec 2017 11:26:44 +0300 (MSK) (envelope-from maxim.konovalov@gmail.com) Date: Fri, 15 Dec 2017 11:26:44 +0300 (MSK) From: Maxim Konovalov To: Eitan Adler cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Fri, 15 Dec 2017 11:33:41 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2017 08:26:53 -0000 Hi Eitan, On Thu, 14 Dec 2017, 20:15-0800, Eitan Adler wrote: > Hi all, > > I've been attempting to maintain bsd-family-tree (available as > share/misc/bsd-family-tree) as a plain text file across 3 different > operating systems: NetBSD, DragonFly, and FreeBSD. > > It has to be maintained by hand, and can't be parsed to do anything > more useful (like turn it into an image). In addition, formatting > differences between the different projects have led to minor > differenes that are difficult to merge. > > I'd like to turn this into into a dot file > (https://en.wikipedia.org/wiki/DOT_(graph_description_language)) which > is a more natural format for a graph. > How does this solve the maintanance issue across different OSes? > Any objections? It isn't used for much beyond documentation so > changing the format isn't expected to cause any negative effects. > Today it is very simple plaintext thing. For me, the complexity will overweight the value of this file. -- Maxim Konovalov