Fw: Re: FCEUX

[John Arntz]

Andrea,

I was able to contact someone from upstream, and I got the reply below. What is the proper way to proceed if upstream is unwilling to use the system library? Should we drop lua support all together? I know you said the lua features are what make fceux stand out as a good emulator, but I'm not sure we can have it, if upstream is unwilling to use system libraries.

Regards,
John

--- On Sat, 1/16/10, Matthew Gambrell <mgambrell at gmail.com> wrote:

> From: Matthew Gambrell <mgambrell at gmail.com>
> Subject: Re: FCEUX
> To: "John Arntz" <jsarntz at yahoo.com>
> Date: Saturday, January 16, 2010, 2:23 PM
> For issue 1, nothing I can do about that,
> although we are currently considering how to better
> communicate with people since mailing lists are apparently
> not reliable. I'll let you know when we change
> anything.
> 
> For issue 2, I suggest you investigate the way lua is
> commonly used and what it is intended for, specifically the
> way it is meant to be compile-time customized and embedded
> in programs. Your distro's policy is not applicable to
> lua, and if they are applying it, then they are wrong, and
> you need to argue with them about that.  In general, what
> are we supposed to do if we are using a library that has
> been heavily modified? Wouldn't we have no choice but to
> drop it into our source tree?
> 
> 
> 
> For issue 3, this hasn't stopped any number of other
> distros from packaging fceux.  Perhaps you should see how
> theyve dealt with it. In fceux, it is not such a big deal
> since there are only two applications really, but what are
> larger projects with more buildable targets in their source
> tree supposed to do? Cut a dozen tarballs out of the source
> tree? 
> 
> 
>  
> On Sat, Jan 16, 2010 at 12:42 PM,
> John Arntz <jsarntz at yahoo.com>
> wrote:
> 
> 
> Greetings,
> 
> 
> 
> My name is John Arntz, and I and one of the people
> attempting to package FCEUX for http://rpmfusion.org which
> is a repository for Fedora RPM packages that cannot be
> packaged in Fedora itself for various reasons. I'm
> writing you because I am having a couple issues.
> 
> 
> 
> 
> 
> The first issue I am having is that I would have posted
> this on the discussion mailing list, however I am having
> trouble subscribing. I have filled out the request, but have
> not yet gotten back a confirmation E-Mail. I used this
> E-Mail address to subscribe with.
> 
> 
> 
> 
> 
> Second, the main issue preventing us from making a package
> is the fact that FCEUX uses Lua statically. RPM Fusion
> follows the Fedora packaging guidelines, which state that a
> package must be built using system provided libraries. The
> problem I am encountering is that FCEUX will not compile
> with the system provided Lua because one of your source
> files requires header files from the static Lua source.
> Specifically, in lua-engine.cpp, line 1064 where the comment
> says if this line crashes, your header files are out of sync
> with lua lib. Fedora is using the current header files that
> came with the latest version of lua, so AFAIK that is not
> the issue. I need to know is what I need to fix to make
> FCEUX compile using the system provided libraries.
> 
> 
> 
> 
> 
> The third issue is that FCEUX/GFCEUX should be split into
> two separate tarballs. This is more of a minor issue, but it
> would be easier for packages if these two peices of software
> were in their own tarballs.
> 
> 
> 
> I love FCEUX. It is my favorite NES Emulator, so that's
> why I chose to try to package it for RPM Fusion. Any
> assistance you could provide to make this possible would be
> greatly appreciated.
> 
> 
> 
> Regards,
> 
> 
> 
> John S. Arntz