From owner-cvs-all Mon Aug 20 8:14:38 2001 Delivered-To: cvs-all@freebsd.org Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by hub.freebsd.org (Postfix) with ESMTP id 34BE737B408; Mon, 20 Aug 2001 08:14:28 -0700 (PDT) (envelope-from dan@lists.unixathome.org) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.1/8.11.1) with ESMTP id f7KFE2044149; Tue, 21 Aug 2001 03:14:02 +1200 (NZST) (envelope-from dan@lists.unixathome.org) From: "Dan Langille" Organization: novice in training To: Johann Visagie Date: Mon, 20 Aug 2001 11:13:53 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: cvs commit: ports/biology/p5-bioperl-devel Makefile ports/biology/p5-bioperl-devel/files Makefile.man Reply-To: dan@langille.org Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Message-ID: <3B80F0F1.3282.57FA006@localhost> In-reply-to: <20010820161028.G67741@fling.sanbi.ac.za> References: <3B80D46A.3260.51031F7@localhost>; from dan@langille.org on Mon, Aug 20, 2001 at 09:12:10AM -0400 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A repost with additional thoughts. On 20 Aug 2001, at 16:10, Johann Visagie wrote: > Dan Langille on 2001-08-20 (Mon) at 09:12:10 -0400: > > > > Any reason not to call it Makefile.inc ? I've seen that used many > > times before. > > No particular reason, except that I was copying what was done to > security/heimdal in this case and didn't engage the brain to think up a > filename of my own. :-) > > I've used Makefile.inc myself in the past, but I don't think there's a > particular rule involved here(?) OK.... [imagine me going to FreshPorts to add Makefile.man to the list of special files] Actually, that should be files/Makefile.man. I think we should have some consistency here. If only for sanity sake. At worst, I'll have to start extending the list of "special files" in FreshPorts. At best, it looks sloppy to have different file names for each type. Is there an established practice in this area of ports? [I'm not counting security/heimdal as established as that's only just occurred]. Personally, I'd like to see a standard set and used. It would make the running of FreshPorts much easier. I'd rather not make changes each time a new file name is conceived. I propose we use Makefile.inc and not put it into files. Anyone concur? > One thing, though: I put my Makefile.man in ${FILESDIR} - I > thought that was neater. I'm not sure that's any neater at all. -- Dan Langille - DVL Software Limited FreshPorts - http://freshports.org/ - the place for ports To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message