From owner-freebsd-arch Thu Jun 14 10:48:30 2001 Delivered-To: freebsd-arch@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C998737B401; Thu, 14 Jun 2001 10:48:21 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5EHm3165036; Thu, 14 Jun 2001 10:48:08 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010614084104.D76016@prism.flugsvamp.com> Date: Thu, 14 Jun 2001 10:48:07 -0700 (PDT) From: John Baldwin To: Jonathan Lemon Subject: sysorg: sys/contrib Cc: arch@FreeBSD.org, Ruslan Ermilov Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Jun-01 Jonathan Lemon wrote: > On Thu, Jun 14, 2001 at 01:07:54PM +0300, Ruslan Ermilov wrote: >> Hi! >> >> There are some problems with the current location of IPFilter sources. >> >> 1. The idea of http://people.freebsd.org/~jhb/docs/sysorg.txt was >> that src/sys/contrib/ mirrors the structure of src/sys/; this is >> currently broken. src/sys/contrib/ipfilter/netinet/ should have >> been actually called the src/sys/contrib/netinet/. > > I'm ambivalent on this. On one hand, having the additional directory > level nicely categorizes the nature of the sys/contrib bits in the same > sense that /src/contrib does, and makes it easier to remove. OTOH, > this might get messy at some point. I can see the value in contrib/ipfilter. sysorg.txt is not set in stone. :) For 3rd party software, it is better if we let the software keep it's distributed layout. The intention was that if you had device driver xyz, then it's sources would be in sys/contrib/dev/xyz/ and under that subdirectory it would follow the internal layout of the package. If we had a networking subdirectory, then sys/contrib/net/ipfilter would be the way to go, but since networking all lives at the top level, sys/contrib/ipfilter is probably fine. Thus, some examples that might help illustrate: sys/contrib/fs/my_spiffs_fs/ sys/contrib/dev/my_spiffy_device_driver/ sys/contrib/vm/my_spiffy_vm_pager/ sys/contrib/my_spiffy_networking_code/ sys/contrib/my_spiffy_kernel_debugger/ sys/contrib/compat/3rd_party_foo_os_emulation/ sys/contrib/lib/my_spiffy_kernel_library/ sys/contrib/boot/my_spiffy_boot_loader/ -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message