This is part of the usual for discussing new virtuals before addition. I'm reaching the final stages of prep for migrating from app-emulation/wine to several packages, one for each major patchset that we support. This will enable us to get releases out quicker. In addition, with the new packaging, we'll be supporting slotting, so users can choose to support specific apps with specific wine versions or patchsets simultaneously. More specifics on that to come in an email about a news item.
I'm not planning on immediately switching over, but rather masking for maybe a month or so before releasing to the public at large. -- NP-Hardass
# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
DESCRIPTION="Virtual for WINE that supports multiple variants and slotting"
HOMEPAGE=""
SRC_URI=""
LICENSE=""
SLOT="0"
KEYWORDS="~amd64 ~x86"
IUSE="staging d3d9"
DEPEND=""
# Note, the ordering here is intentional, to take advantage of the short-circuit
# logic of portage, to enforce wine-vanilla as default for new users. The idea
# behind this is that some USE flags may pull in 3rd-party patchsets, so default
# of vanilla prevents that.
RDEPEND="
staging? ( || (
app-emulation/wine-staging[staging]
app-emulation/wine-any[staging]
) )
d3d9? ( || (
app-emulation/wine-d3d9[d3d9]
app-emulation/wine-any[d3d9]
) )
|| (
app-emulation/wine-vanilla
app-emulation/wine-staging
app-emulation/wine-d3d9
app-emulation/wine-any
)
!app-emulation/wine:0"
signature.asc
Description: OpenPGP digital signature
