https://bugzilla.redhat.com/show_bug.cgi?id=835686
--- Comment #5 from Andreas Bierfert <andreas.bierfert(a)lowlatency.de> ---
I am fine with it either way. However, if we decide on wine-mono we should
rename the gecko stuff accordingly...
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835686
Kalev Lember <kalevlember(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kalevlember(a)gmail.com
--- Comment #4 from Kalev Lember <kalevlember(a)gmail.com> ---
Regarding the naming issue that Erik pointed out:
The MinGW Packaging Guidelines are for library packages that can be used for
building Windows apps. But this package is different; it only installs a .msi
and no dlls / header files and is apparently only meant for use within Wine.
As such, perhaps it would be clearer if it's called 'wine-mono'? This package
is really just another component for the wine stack, even though it's built
using the mingw cross compiler. I don't think the mingw naming guidelines are
applicable here.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835686
--- Comment #2 from Andreas Bierfert <andreas.bierfert(a)lowlatency.de> ---
Yes this is intentional. I'd prefer a setup like wine-gecko but this is what
wine currently supports.
Here is the quote from: http://wiki.winehq.org/Mono
"Unlike gecko, there is only one package containing the code for both x86 and
x86_64, as most of the code does not depend on the architecture."
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835863
Jan Lieskovsky <jlieskov(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |835864
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835863
Jan Lieskovsky <jlieskov(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |c.david86(a)gmail.com,
| |ccoleman(a)redhat.com,
| |drizt(a)land.ru,
| |erik-fedora(a)vanpienbroek.nl
| |,
| |fedora-mingw(a)lists.fedorapr
| |oject.org,
| |ktietz(a)redhat.com,
| |lfarkas(a)lfarkas.org,
| |mnowak(a)redhat.com,
| |paul(a)city-fan.org,
| |rjones(a)redhat.com,
| |seceng-idm-qe-list(a)redhat.c
| |om
CC| |tkramer(a)redhat.com,
| |veillard(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835686
Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |erik-fedora(a)vanpienbroek.nl
--- Comment #1 from Erik van Pienbroek <erik-fedora(a)vanpienbroek.nl> ---
I see you're not using mingw32-wine-mono or mingw64-wine-mono binary package
names but put the .msi file in a binary rpm named mingw-wine-mono. Is this
intentional? Does it contain both the win32 and win64 pieces?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=835686
Andreas Bierfert <andreas.bierfert(a)lowlatency.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fedora-mingw(a)lists.fedorapr
| |oject.org
--
You are receiving this mail because:
You are on the CC list for the bug.