the ebuild must be added to portage tree for testing Reproducible: Always Steps to Reproduce:
Created attachment 232809 [details] working ebuild
The Wine development release 1.2-rc1 is now available.
The Wine development release 1.2-rc1 is now available. This is the first release candidate for Wine 1.2. It marks the beginning of the code freeze period. Please give this release a good testing to help us make 1.2 as good as possible. What's new in this release (see below for details): - Many new toolbar icons. - Support for alpha blending in image lists. - Much more complete shader assembler. - Support for Arabic font shaping and joining. - A number of fixes for video rendering. - Font antialiasing configuration through fontconfig. - Improved handling of desktop link files. - Various bug fixes.
Comment on attachment 232809 [details] working ebuild post diffs, not entire files. but if you havent made any changes to the existing ebuild, dont even post it please.
Yesterday 1.2_rc2 has been released. See http://www.winehq.org/news/2010052801
Created attachment 233483 [details, diff] wine-1.2_rc2.ebuild.patch Ordered all deps alphabeticaly, same for configure lines (handy scriptie :P). Added missing / weird deps (ttf-fonts, emul-opengl). Added dies where should be and added bit sane comments to them. This patch should be applied also to live version.
Created attachment 233555 [details] app-emulation/wine-1.2_rc2 ebuild Here is a WINE app-emulation/wine-1.2_rc2 to spare people the trouble of applying the patch to the existing ebuild.
(In reply to comment #4) > (From update of attachment 232809 [details]) > post diffs, not entire files. but if you havent made any changes to the > existing ebuild, dont even post it please. > Sorry, I had not seen your comment. Why do you want people to post patch files instead of ebuilds?
(In reply to comment #8) > (In reply to comment #4) > Sorry, I had not seen your comment. Why do you want people to post patch files > instead of ebuilds? > We don't care about usability from bugzilla directly, but it is way easier for us as developers to review patches. If you upolad whole ebuild we have to do diff ourselves and it slows things up :]
sorting one ebuild will diverge from all the others. that's a pita not worth it.