| Summary: | Suggestion: WINE development ebuilds | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Brad Laue <brad> |
| Component: | Current packages | Assignee: | Wine Maintainers <wine> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | sarnex |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | WINE 2.12 ebuild | ||
Sorry - minor correction -
"${FILESDIR}"/${PN}-1.7.12-osmesa-check.patch #429386
does need to be removed.
Thanks for your work, however, this command might open your eyes: $ equery l -p wine* ...d'oh. :-) |
Created attachment 486620 [details] WINE 2.12 ebuild I'd like to suggest adding the development releases of WINE to the portage tree. The 2.3 (which I'm assuming is some intermediate update to stable) and -9999 ebuilds work well, but the devel releases are a nice predictable set of milestones. I've bumped the wine-2.3 ebuild to 2.12 in my own tree and it builds with all USE flags enabled without further modification - looks like the current ebuild abstracts things pretty nicely.