From owner-freebsd-ports Wed Nov 20 1:19:47 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5656437B401 for ; Wed, 20 Nov 2002 01:19:46 -0800 (PST) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE3BC43E75 for ; Wed, 20 Nov 2002 01:19:44 -0800 (PST) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.12.6/8.12.6) with ESMTP id gAK9JWx2050404; Wed, 20 Nov 2002 09:19:32 GMT (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost) by happy-idiot-talk.infracaninophile.co.uk (8.12.6/8.12.6/Submit) id gAK9JQQK050403; Wed, 20 Nov 2002 09:19:26 GMT Date: Wed, 20 Nov 2002 09:19:26 +0000 From: Matthew Seaman To: Ng Pheng Siong Cc: ports@FreeBSD.ORG Subject: Re: 5.0-CURRENT build failure of ports you maintain Message-ID: <20021120091926.GA50113@happy-idiot-talk.infracaninophi> References: <200211180106.gAI16QfG085711@bento.FreeBSD.org> <20021119154932.GA476@vista.netmemetic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021119154932.GA476@vista.netmemetic.com> User-Agent: Mutt/1.5.1i X-Spam-Status: No, hits=-2.2 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_05_08, USER_AGENT,USER_AGENT_MUTT version=2.43 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Nov 19, 2002 at 11:49:32PM +0800, Ng Pheng Siong wrote: > On Sun, Nov 17, 2002 at 05:06:26PM -0800, Kris Kennaway wrote: > > One or more ports that you maintain are currently unbuildable under > > FreeBSD 5.0-CURRENT/i386 on the FreeBSD package-building cluster. > (Dunno if I'm talking to a mailing list... ;-) Yes you are. > Anyways, I know why the port breaks, but I'm not familiar with this ports > stuff. Do you have pointers to what a port maintenance guy should do? The porter's handbook should tell you everything you need to know about how the ports system works: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Essentially you should submit a problem report using send-pr(1): Category 'Ports', Class 'maintainer-update', containing the port changes you want to make as patches preferably in 'diff -u' format. That often means sending a diff against another diff file for the stuff in the .../files subdirectory. If your patches make any files redundant note them down in the PR so the committer can 'cvs remove' them. > (I'm the original developer of the software in question; the port wasn't > created by me, but I have agreed to take over its maintenance.) It's the same procedure when you release a new version of the software -- send in a PR with the changes to the port Makefile, etc. If you take a look at the archives of the freebsd-ports@freebsd.org mailing list, there are many examples: http://docs.freebsd.org/mail/archive/2002/freebsd-ports/ Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message