Date: Wed, 4 Aug 2004 17:28:13 -0600 From: Travis Poppe <tlp@LiquidX.org> To: Roman Neuhauser <neuhauser@chello.cz> Cc: freebsd-ports@freebsd.org Subject: Re: Porting Mupen 64 to FreeBSD. 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 5 Aug 2004 00:51:42 +0200 Roman Neuhauser <neuhauser@chello.cz> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040804172813.5e0754b1>