Le lun 20/09/2004 � 10:53, Mike Hearn a �crit : > > We should have a binary package on our SF site. > > Well, do you mean a package of drop-in files for your virtual windows > drive? If so then I agree, but it'd make sense to have some support for > this in wineprefixcreate, something like: > > overlay_dir="@libdir@/wine/windows-drive-binary-overlay" > if [ -d "$overlay_dir" ]; then > cp -r "$overlay_dir" $WINEPREFIX/drive_c/ > fi > > And then the binary package can just be a tarball you can extract to > /usr/lib/wine or somesuch (lib as it's not arch-neutral).
I'd prefer a tarball extracted during wineprefixcreate, but that's only a preference. Which files (except the Mozilla Active X) is not arch-neutral? Fonts are, stdole32.tlb (as created by the Codeweavers program) is. > > In theory then binary packagers would include them in their packages. In > practice quite a lot of users either install Wine from the source, or > use packages built by people who don't track Wine development (*cough* > gentoo *cough*) so this wouldn't solve the problem for a lot of people. I tried to contact the author of the Gentoo Wine ebuild with a patch enhancing it, 3 times even, still no answer to this date. Any Gentoo users reading this? Anyone knows why he doesn't answer? Or wanting to do a takeover of the ebuild? > > Perhaps a notice at the end of the configure script in big loud letters > saying "YOU SHOULD DOWNLOAD HTTP://WHATEVER/! DO IT! DO IT NOW!" would > help. > > Some packagers quite clearly ignore changes in Wine itself and just bump > the date when there's a new release, but I don't think there's anything > we can do about that except have a generic downloader program which > would download the binary package as needed. That'd be very silly > indeed. Probably best to just let those users lose. > Vincent
