From owner-freebsd-hackers@freebsd.org Thu Dec 28 15:42:56 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 9F0CCEA5670 for ; Thu, 28 Dec 2017 15:42:56 +0000 (UTC) (envelope-from julian@freebsd.org) 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 78DA27FF02 for ; Thu, 28 Dec 2017 15:42:56 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-0-128.dyn.iinet.net.au [115.166.0.128]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id vBSFghdT004392 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 28 Dec 2017 07:42:48 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: Objections to converting bsd-family-tree to a dot file To: Eitan Adler , Maxim Konovalov Cc: FreeBSD Hackers , tech-misc@netbsd.org, Kernel@dragonflybsd.org References: From: Julian Elischer Message-ID: <14e0e227-4d9d-4eba-da1d-90c192bbc251@freebsd.org> Date: Thu, 28 Dec 2017 23:42:37 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US 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: Thu, 28 Dec 2017 15:42:56 -0000 On 15/12/17 4:51 pm, Eitan Adler wrote: >> Show Me The Money! > See examples at the bottom > > >> How easy would it be to render something like the existing > bsd-family-tree, e.g. something that is reasonably intelligent when > viewed with more(1) or less(1) with the same basic information that > it has now? > > Pretty easy. Examples below. Note its just a first draft. That said, I > did find several unconnected nodes: some of which are corrected in > this version. > >> Also, would rendering it be something that can reasonably > be done while building the system, or would it need to be pre-rendered > and the result checked into the SCM (keep in mind that NetBSD's > build.sh is portable, i.e. you can build NetBSD on Windows if you > feel like it)? > > It'll likely be easier to check it to the repo. It can be done > reasonably portably using graphviz, but its not likely worth it. > > >>> 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. the current manually done file is easy to read. I can't work out if one of the files in the directory you show below is an automatically made version, but the graphically rendered files there are a mess and way harder to read. (and of course not ascii). If there is an ascii generated file that is as easy to read then ok but it's going to have to be VERY good to be more readable that what is there already. > It isn't really complex: > https://people.freebsd.org/~eadler/files/family-tree/by-hand-1.dot.txt > https://people.freebsd.org/~eadler/files/family-tree/ > > >