From owner-freebsd-ports Sat Sep 23 17:22: 7 2000 Delivered-To: freebsd-ports@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 0161B37B61B for ; Sat, 23 Sep 2000 17:21:51 -0700 (PDT) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.144.21]) by po4.glue.umd.edu (8.10.1/8.10.1) with ESMTP id e8O0Lmk03795; Sat, 23 Sep 2000 20:21:48 -0400 (EDT) Message-ID: <39CD491F.C0AE18F7@glue.umd.edu> Date: Sat, 23 Sep 2000 20:21:51 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.74 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Trevor Johnson Cc: ports@FreeBSD.ORG Subject: Re: ports tree idea: Combine DESCR and COMMENT References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Trevor Johnson wrote: > 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. I like the COMMENT variable idea. How does that effect making the INDEX file and the port directory web pages? These all sound like good ideas to me, why didn't anything ever come of it? -Brandon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message