From owner-freebsd-ports@FreeBSD.ORG Wed Aug 4 23:27:53 2004 Return-Path: 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 E9DED16A4CE for ; Wed, 4 Aug 2004 23:27:53 +0000 (GMT) Received: from mail.cableone.net (scanmail2.cableone.net [24.116.0.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A46543D2F for ; Wed, 4 Aug 2004 23:27:53 +0000 (GMT) (envelope-from tlp@LiquidX.org) Received: from maya.liquidx.org (unverified [24.119.12.253]) by smail2.cableone.net (SurgeMail 1.9b) with ESMTP id 11612203 for multiple; Wed, 04 Aug 2004 16:13:20 -0700 Date: Wed, 4 Aug 2004 17:28:13 -0600 From: Travis Poppe To: Roman Neuhauser Message-Id: <20040804172813.5e0754b1@maya.liquidx.org> In-Reply-To: <20040804225141.GB535@isis.wad.cz> References: <20040804100024.4e8e4ce5@maya.liquidx.org> <20040804225141.GB535@isis.wad.cz> X-Mailer: Sylpheed version 0.9.11claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: freebsd-ports@freebsd.org Subject: Re: Porting Mupen 64 to FreeBSD. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Aug 2004 23:27:54 -0000 On Thu, 5 Aug 2004 00:51:42 +0200 Roman Neuhauser wrote: > # tlp@LiquidX.org / 2004-08-04 10:00:24 -0600: > > I would like someone else to create the individual ports for all the > > plugins Mupen 64 uses (without them, the emulator itself is > > useless). > > > > The idea of porting the plugins scares me away every time, even > > though there are only like 5 or 6 of them. Most of them build with > > little modification out of the box (or atleast the versions I used > > in 2003 did). > > What's so scary about the porting then? (honest question) Each plugin is different and requires separate porting work. It's not so much that it's scary, but I already maintain 10 or so ports and don't want to maintain all the individual plugins on my own. My original idea was to create a single port called mupen64-plugins that contained them all, and that turned into a huge mess. I suppose that's the main reason I remember it being scary. Since then I just never got back to working on the ports again, and decided that if I were to continue it I'd rather have some help maintaining them. -tlp