Some thoughts about firmware inclusion.

[King InuYasha]

The problem I see with including Win32 binaries in the current state of
things is that Fedora DOES NOT have the MinGW cross-tools packages
available. I hope that with GCC4 being available for MinGW that someone
would take the incentive to package MinGW for Fedora (I am not skilled
enough to do it!), which then will permit rpmbuild to be able to build Win32
based programs from source to install. Though at the moment, I don't think
it would be possible to package VirtualDub with the current rules regarding
binaries of this nature since at the moment, no one has made VirtualDub
buildable using a makefile system + GCC. Also, VirtualDub requires MASM
currently, though Avery Lee was considering switching to YASM at one point.
Though PopAsm could fix that problem (it can build MASM assembly code). If
there was a way to turn MSVC2005 solutions and project files into makefiles,
then it could possibly be packaged in Fedora.

On 10/25/07, Adam Jackson <ajackson at redhat.com> wrote:
>
> On Thu, 2007-10-25 at 16:43 +0200, Hans de Goede wrote:
> > Adam Jackson wrote:
> > > I suppose, if I had to think about it, that the policy on game data
> sort
> > > of contradicts this nice clean delineation, since game data files
> often
> > > include a scripting language for in-game logic.  That's not
> necessarily
> > > a problem, merely an exception.  Personally I'm fine with it, but it
> > > seems difficult to construct a (non-emotional) justification for it
> that
> > > doesn't expand to cover win32 binaries or ROMs without source.
> >
> > Well written, and I fully agree, except that besides an exception for
> game
> > data, I would also like to see an exception for system ROM's for old
> computers
> > like the amstrad, where amstrad has been so kind to allow free
> redistribution
> > of the roms. I'm not advocating to make the same exception for software
> that
> > ran on these old computers, merely for the code that was in ROM's
> _inside_ the
> > sytem and thus is needed for the emulator to function _at all_, to me
> this
> > clearly is firmware.
>
> Yeah, that's pretty clearly firmware to me too.
>
> - ajax
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20071026/dcb3a6a5/attachment.htm>