From owner-freebsd-hackers@freebsd.org Fri Dec 15 08:51:50 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 7A3C3E9FD6B for ; Fri, 15 Dec 2017 08:51:50 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36BA26D6E5 for ; Fri, 15 Dec 2017 08:51:50 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x229.google.com with SMTP id t127so5546768ybf.9 for ; Fri, 15 Dec 2017 00:51:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=691T1LZ2GmUQhJX2EOI4vQkjvJGS7GBpaP1NyB9UrUE=; b=Uef+N+x6dmfjB+uHC2doSacNy9YBYxnGsm80QBMFe9/UGt11LN51erKg6TQtMlA8sH W8TcD247xoTNyQ3CEbOmtOxgSMfHMJvPcJatXsoHR0aWjQIZdwnPBKeJCut811KwhAbw oZ0aGsMU/ilfMw0UgL/dt9UuXroN6xkzECVvM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=691T1LZ2GmUQhJX2EOI4vQkjvJGS7GBpaP1NyB9UrUE=; b=baoOOWLwzCKdWs6De35j7hedyDD8pxdVqvIDNwfpnyQkO9whV4oojCoatkvLNq5V2W Tj98Ge3Opx4jax/if2Io0KehrYaz5VGiyR2vldDDJAQOHF+H7jbyBiMceMxDhY+2s9B4 DClredFrML7Chl5/e3/yHOtBGZTUmwV9BaO7BXsrfvcvpcvzk+ztqFbOEgZs1MduG+xt OM8wIXX/zNZn/F1pbs3yGv8uhvVfszxKTNThKZow/+qylaz/tkIzsV4GK73MCWpt0SX3 yC2y2cLv5dfL0i8ho1a6FvkPvToif/Z/6HMogIw/p9XmkDJNaMgtmhmkZ7SkWHixdK0e 8lYw== X-Gm-Message-State: AKGB3mIuVk1HmEkSDRP+ZHiI7idcU5E23g0nV5RUJ2jDVu2AYSoeGMaB +4zwEsHv1zZ1G76rgyrt4bnk2zzct78iwiKgEnsbhw== X-Google-Smtp-Source: ACJfBovXunQ5FdR+dIgBuwCQBlUy2zO5ICeOL/Tl12uVI9sK807Z1qUGvv0/koHyWDI4/muDzh59rhdOCRW7CAl/13g= X-Received: by 10.37.136.7 with SMTP id c7mr6644376ybl.171.1513327909262; Fri, 15 Dec 2017 00:51:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Fri, 15 Dec 2017 00:51:18 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Fri, 15 Dec 2017 00:51:18 -0800 Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: Maxim Konovalov Cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Content-Type: text/plain; charset="UTF-8" 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:51:50 -0000 > 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. 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/ -- Eitan Adler