From owner-freebsd-standards@FreeBSD.ORG Fri May 26 11:19:51 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5ED516A43D for ; Fri, 26 May 2006 11:19:51 +0000 (UTC) (envelope-from schweikh@schweikhardt.net) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B3C43D53 for ; Fri, 26 May 2006 11:19:50 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 2264124B250; Fri, 26 May 2006 13:19:49 +0200 (CEST) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) by hal9000.schweikhardt.net (8.13.6/8.13.6) with ESMTP id k4QBIn2d040013 for ; Fri, 26 May 2006 13:18:49 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.6/8.13.6/Submit) id k4QBInsn040012 for freebsd-standards@freebsd.org; Fri, 26 May 2006 13:18:49 +0200 (CEST) (envelope-from schweikh) Date: Fri, 26 May 2006 13:18:49 +0200 From: Jens Schweikhardt To: freebsd-standards@freebsd.org Message-ID: <20060526111849.GA35337@schweikhardt.net> References: <20060526082721.GA83222@medusa.sysfault.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060526082721.GA83222@medusa.sysfault.org> User-Agent: Mutt/1.5.11 Subject: Re: Import of the cflow utility to conform to POSIX X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 11:19:51 -0000 On Fri, May 26, 2006 at 10:27:21AM +0200, Marcus von Appen wrote: # Hi, # # I wonder, if someone is working on that task to create a POSIX compliant # cflow utility[0] on basis of the cflow implementation in the ports. If # not, I would like to take over that task (as I am working on it # devel/cflow anyways at the moment). I haven't heard of anyone working on this. I suspect not many people these days miss cflow, and the few that do simply use devel/cflow. # Whom would be the responsible to get into detail about it? This list is most likely the best place. I expect some argument about making it part of src/ when a port is available. You would counter that if your version does something that devel/cflow can not do or your version does better. As a minimum requirement it would have to correctly process what we have in the src tree. (I never tested if devel/cflow can do this). As for basing your work on devel/cflow, I looked at the source and it says it was put in the public domain by Andrew Moore. However there are a lot of other authors mentioned. IANAL, but I question if someone can put something in the PD if it's not 100% his own and without asking all other contributors. To avoid all these questions, a reimplementation from scratch with ideas (but not verbatim code) taken from devel/cflow would be best. A BSD licensed and style(9) conformant result would certainly be appreciated. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)