From owner-freebsd-ports Sat Sep 23 15: 7:50 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id 8230737B422 for ; Sat, 23 Sep 2000 15:07:48 -0700 (PDT) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e8NM7lt17497; Sat, 23 Sep 2000 18:07:47 -0400 (EDT) Date: Sat, 23 Sep 2000 18:07:47 -0400 (EDT) From: Trevor Johnson To: Brandon Fosdick Cc: ports@FreeBSD.ORG Subject: Re: ports tree idea: Combine DESCR and COMMENT In-Reply-To: <39CD200B.A10214EA@glue.umd.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Since people complain about the number of inodes that the ports tree uses I was > thinking that maybe the pkg/DESCR and pkg/COMMENT files could be combined. Since > the COMMENT file is usually only one line it seems that that one line could > easily be made the very first line of DESCR. > > Now obviously this only saves one inode per port, but when you have over 3000 > ports it starts to add up. Is this something that could be done while we're > waiting for the new reincarnation of the ports tree? > This was proposed on 14 February by Jeremy Lea in the "multi-level categories" thread. Some other ideas that struck me as worthy: - move everything from the patches/ and pkg/ directories into the top-level directory for each port - permit more than one source file to be changed by each patch file, when the maintainer prefers to work with such patches - move files/md5 to the top-level directory, and only have a files/ directory when it is needed for other files (few ports have these) Another possibility for the comments is to make them a line in the makefiles: COMMENT= "Andrew User Interface System" Someone said that many DESCR files already have the comment as their first line, though. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message