Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
wine: questions on recent changes
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo
View previous topic :: View next topic  
Author Message
danboston
n00b
n00b


Joined: 17 Nov 2016
Posts: 47

PostPosted: Tue Apr 11, 2017 7:07 pm    Post subject: wine: questions on recent changes Reply with quote

After an "emerge world" I found one news item. eselect news read yielded an interesting notice about wine being split into multiple packages. An excerpt:
Quote:
Starting with Wine 2.0, Wine in Gentoo is transitioning away from its
traditional packaging and toward a new, split and slotted, Wine.

As many Wine users know, there are often regressions or an application
works better on one version of wine than another. Going forward,
packaging in Gentoo will allow simultaneous installation of multiple
versions of Wine.

Additionally, to expedite vanilla releases as well as permit multiple
configurations for each Wine installation, the major patchsets have
been split out into separate packages.

Going forward, app-emulation/wine will transition to:
app-emulation/wine-vanilla: upstream Wine with no external patchsets
(like if the old packaging forced USE="-staging -d3d9")
app-emulation/wine-staging: Wine with Wine-Staging's patchset
(like if the old packaging forced USE="+staging -d3d9")
app-emulation/wine-d3d9: Wine with Ixit's Gallium Nine patchset
(like if the old packaging forced USE="-staging +d3d9")
app-emulation/wine-any: Wine with any of the patchsets or flags
(exactly like the old packaging regarding USE flags)

With some trepidation, I began the emerge world...
Code:
~# emerge --ask --update --deep --newuse @world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] media-libs/zimg-2.5 [2.4]
[ebuild     U  ] media-libs/harfbuzz-1.4.5 [1.3.1]
[ebuild     U  ] net-libs/webkit-gtk-2.16.1 [2.14.5]
[ebuild     U  ] games-puzzle/sgt-puzzles-20170228 [20160315]
[ebuild     U  ] www-plugins/adobe-flash-25.0.0.148 [25.0.0.127]

Would you like to merge these packages? [Yes/No]

No upgrades to wine. So it seems that wine has not yet changed to the new multiple-wines form?

One more thing to check:
Code:

~# emerge --search wine
[ Results for search key : wine ]
Searching...

*  app-emacs/whine
      Latest version available: 20091222
      Latest version installed: [ Not Installed ]
      Size of files: 5 KiB
      Homepage:      http://www.emacswiki.org/emacs/Whine
      Description:   Complaint generator for GNU Emacs
      License:       public-domain

*  app-emulation/q4wine
      Latest version available: 1.3.1
      Latest version installed: [ Not Installed ]
      Size of files: 2,797 KiB
      Homepage:      http://q4wine.brezblock.org.ua/
      Description:   Qt GUI configuration tool for Wine
      License:       GPL-3

*  app-emulation/wine
      Latest version available: 2.0
      Latest version installed: 2.0
      Size of files: 165,443 KiB
      Homepage:      http://www.winehq.org/
      Description:   Free implementation of Windows(tm) on Unix
      License:       LGPL-2.1

*  app-emulation/wine-any [ Masked ]
      Latest version available: 9999
      Latest version installed: [ Not Installed ]
      Size of files: 98 KiB
      Homepage:      http://www.winehq.org/
      Description:   Free implementation of Windows(tm) on Unix
      License:       LGPL-2.1

*  app-emulation/wine-d3d9 [ Masked ]
      Latest version available: 9999
      Latest version installed: [ Not Installed ]
      Size of files: 98 KiB
      Homepage:      http://www.winehq.org/
      Description:   Free implementation of Windows(tm) on Unix
      License:       LGPL-2.1

*  app-emulation/wine-desktop-common [ Masked ]
      Latest version available: 20150204
      Latest version installed: [ Not Installed ]
      Size of files: 98 KiB
      Homepage:      https://github.com/NP-Hardass/wine-desktop-common http://dev.gentoo.org/~tetromino/distfiles/wine http://bazaar.launchpad.net/~ubuntu-wine/wine/ubuntu-debian-dir/files/head:/debian/
      Description:   Various desktop menu items and icons for wine
      License:       LGPL-2.1

*  app-emulation/wine-gecko [ Masked ]
      Latest version available: 2.47-r1
      Latest version installed: [ Not Installed ]
      Size of files: 97,727 KiB
      Homepage:      https://winehq.org
      Description:   A Mozilla Gecko based version of Internet Explorer for Wine
      License:       Apache-2.0 BSD BSD-2 MIT MPL-2.0

*  app-emulation/wine-mono [ Masked ]
      Latest version available: 4.7.0
      Latest version installed: [ Not Installed ]
      Size of files: 63,111 KiB
      Homepage:      https://www.winehq.org/
      Description:   Wine Mono is a replacement for the .NET runtime and class libraries in Wine
      License:       BSD-2 GPL-2 LGPL-2.1 MIT MPL-1.1

*  app-emulation/wine-staging [ Masked ]
      Latest version available: 9999
      Latest version installed: [ Not Installed ]
      Size of files: 98 KiB
      Homepage:      http://www.winehq.org/
      Description:   Free implementation of Windows(tm) on Unix
      License:       LGPL-2.1

*  app-emulation/wine-vanilla [ Masked ]
      Latest version available: 9999
      Latest version installed: [ Not Installed ]
      Size of files: 98 KiB
      Homepage:      http://www.winehq.org/
      Description:   Free implementation of Windows(tm) on Unix
      License:       LGPL-2.1

*  app-emulation/winetricks
      Latest version available: 20170327
      Latest version installed: [ Not Installed ]
      Size of files: 193 KiB
      Homepage:      http://winetricks.org http://wiki.winehq.org/winetricks
      Description:   Easy way to install DLLs needed to work around problems in Wine
      License:       LGPL-2.1+

*  app-eselect/eselect-wine [ Masked ]
      Latest version available: 1.0
      Latest version installed: [ Not Installed ]
      Size of files: 19 KiB
      Homepage:      http://bitbucket.org/NP-Hardass/eselect-wine
      Description:   Manage active wine version
      License:       GPL-2+

*  app-text/winefish [ Masked ]
      Latest version available: 1.3.3-r2
      Latest version installed: [ Not Installed ]
      Size of files: 475 KiB
      Homepage:      https://github.com/viettug/winefish
      Description:   LaTeX editor based on Bluefish
      License:       GPL-2

*  sec-policy/selinux-wine
      Latest version available: 2.20170204-r2
      Latest version installed: [ Not Installed ]
      Size of files: 1,040 KiB
      Homepage:      https://wiki.gentoo.org/wiki/Project:SELinux
      Description:   SELinux policy for wine
      License:       GPL-2

*  virtual/wine [ Masked ]
      Latest version available: 0-r4
      Latest version installed: [ Not Installed ]
      Size of files: 0 KiB
      Homepage:
      Description:   Virtual for WINE that supports multiple variants and slotting
      License:

*  x11-plugins/wminet
      Latest version available: 3.0.0-r1
      Latest version installed: [ Not Installed ]
      Size of files: 47 KiB
      Homepage:      http://www.swanson.ukfsn.org/#wminet
      Description:   dockapp for monitoring internet connections to and from your computer
      License:       GPL-2

[ Applications found : 16 ]


That shows that the new split wine packages *are* in portage

I have checked my use flags and it seems that I would be using app-emulation/wine-staging in the future.

Do I need to unmerge wine and [re]emerge the other wine?
Back to top
View user's profile Send private message
danboston
n00b
n00b


Joined: 17 Nov 2016
Posts: 47

PostPosted: Tue Apr 11, 2017 7:11 pm    Post subject: Reply with quote

Hmmm.

Between
Code:

*  virtual/wine [ Masked ]
      Latest version available: 0-r4
      Latest version installed: [ Not Installed ]
      Size of files: 0 KiB
      Homepage:
      Description:   Virtual for WINE that supports multiple variants and slotting
      License:

and
Code:

*  app-eselect/eselect-wine [ Masked ]
      Latest version available: 1.0
      Latest version installed: [ Not Installed ]
      Size of files: 19 KiB
      Homepage:      http://bitbucket.org/NP-Hardass/eselect-wine
      Description:   Manage active wine version
      License:       GPL-2+

I think I begin to see a possible answer.
Back to top
View user's profile Send private message
szatox
Veteran
Veteran


Joined: 27 Aug 2013
Posts: 1493

PostPosted: Tue Apr 11, 2017 8:02 pm    Post subject: Reply with quote

Wine, and wine-* are different packages. Any of those satisfies dependencies of virtual/wine, so you can chose the one you like most.
It seems that current app-emulation/wine will be completely dropped from portage, so yes, you will have to uninstall it if you want to keep your gentoo up to date. It doesn't change that much if you were fine with the old approach (the package just changes its name), but it will allow more flexibility, which is really cool.

Good move, maintainers, thanks :)
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1327
Location: United Kingdom

PostPosted: Wed Apr 12, 2017 1:01 am    Post subject: Reply with quote

I'm currently using app-emulation/wine-2.3 and I have the following line in /etc/portage/package/package.use/wine

Code:
app-emulation/wine abi_x86_32 -ldap -pipelight staging


So I added the following lines in preparation for when app-emulation/wine is dropped from the Portage tree and I unmerge it:

Code:
virtual/wine -d3d9 staging
app-emulation/wine-any abi_x86_32 -d3d9 -ldap -pipelight staging


which I hope will keep WINE the same as it is now in my installation when I merge virtual/wine and app-emulation/wine-any and enter:

Code:
# eselect wine set wine-any-2.3


I ssume that will work, as the virtual contains:

Code:
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"

_________________
Clevo W230SS: amd64, OpenRC, nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64, OpenRC, xf86-video-ati, dual booting with Win 7 Pro 64-bit.
KDE on both laptops.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
Chiitoo
Moderator
Moderator


Joined: 28 Feb 2010
Posts: 1399
Location: Here and Away Again

PostPosted: Wed Apr 12, 2017 9:58 am    Post subject: ><)))°€ Reply with quote

danboston,

Indeed, the packages are in Portage already, but they are masked until further tested.

If you were to do something like

Code:
emerge -p wine-any

you should see something like this:

Code:
These are the packages that would be merged:

Calculating dependencies... done!

!!! All ebuilds that could satisfy "wine-any::gentoo" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-emulation/wine-any-9999::gentoo (masked by: package.mask, missing keyword)
/usr/portage/profiles/package.mask:
# NP-Hardass <NP-Hardass@gentoo.org> (10 Apr 2017)
# Masked for testing

- app-emulation/wine-any-2.5::gentoo (masked by: package.mask)
- app-emulation/wine-any-2.4::gentoo (masked by: package.mask)
- app-emulation/wine-any-2.3::gentoo (masked by: package.mask)
- app-emulation/wine-any-2.2::gentoo (masked by: package.mask)
- app-emulation/wine-any-2.1::gentoo (masked by: package.mask)
- app-emulation/wine-any-2.0::gentoo (masked by: package.mask)

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Also if you haven't before, I might recommend giving 'app-portage/eix' a try, as an alternative to 'emerge --search'. It has some features that can make searching a bit more informative. ^^

(So it is possible to install them, but not without performing some extra steps towards it.)

Fitzcarraldo,

That looks about right, though you could just as well go for 'wine-staging' and don't worry about the 'staging' flag, but either will work. :]
_________________
Kind Regards,
~ The Noob Unlimited ~

Sore wa sore, kore wa kore.
Back to top
View user's profile Send private message
Roman_Gruber
Advocate
Advocate


Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria

PostPosted: Wed Apr 12, 2017 1:52 pm    Post subject: Reply with quote

Quote:
app-emulation/wine-d3d9: Wine with Ixit's Gallium Nine patchset


Do i benefit from that when i use the nvidia-drivers binary only?
Back to top
View user's profile Send private message
BobWya
Apprentice
Apprentice


Joined: 12 Aug 2012
Posts: 220
Location: Cambridge,UK

PostPosted: Wed Apr 12, 2017 5:55 pm    Post subject: Reply with quote

Roman_Gruber wrote:
Quote:
app-emulation/wine-d3d9: Wine with Ixit's Gallium Nine patchset


Do i benefit from that when i use the nvidia-drivers binary only?


In a word... no.
_________________
system: G751JT (ASUS-NotebookSKU); processor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz; memory: 32GiB System Memory; display: GM204M [GeForce GTX 970M]; disk: 2048GB Samsung SSD 850;BD-CMB UJ172 S;1024GB Samsung SSD 850
Back to top
View user's profile Send private message
NP-Hardass
Developer
Developer


Joined: 24 Mar 2013
Posts: 34

PostPosted: Wed Apr 12, 2017 7:11 pm    Post subject: Reply with quote

Fitzcarraldo wrote:
I'm currently using app-emulation/wine-2.3 and I have the following line in /etc/portage/package/package.use/wine

Code:
app-emulation/wine abi_x86_32 -ldap -pipelight staging


So I added the following lines in preparation for when app-emulation/wine is dropped from the Portage tree and I unmerge it:

Code:
virtual/wine -d3d9 staging
app-emulation/wine-any abi_x86_32 -d3d9 -ldap -pipelight staging


which I hope will keep WINE the same as it is now in my installation when I merge virtual/wine and app-emulation/wine-any and enter:

Code:
# eselect wine set wine-any-2.3


I ssume that will work, as the virtual contains:

Code:
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"


Actually, the virtual contains an ordering, so in your case, using "-d3d9 staging" on the virtual would cause the variant wine-staging to be used instead of wine-any.
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1327
Location: United Kingdom

PostPosted: Wed Apr 12, 2017 8:59 pm    Post subject: Reply with quote

NP-Hardass wrote:
Actually, the virtual contains an ordering, so in your case, using "-d3d9 staging" on the virtual would cause the variant wine-staging to be used instead of wine-any.

Thanks. So presumably the following for package.use, then (bearing in mind I want the same flexibility with app-emulation/wine-any as app-emulation/wine)?:

Code:
virtual/wine -d3d9
app-emulation/wine-any abi_x86_32 -d3d9 -ldap -pipelight staging

_________________
Clevo W230SS: amd64, OpenRC, nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64, OpenRC, xf86-video-ati, dual booting with Win 7 Pro 64-bit.
KDE on both laptops.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 4809
Location: The Peanut Gallery

PostPosted: Thu Apr 13, 2017 3:52 pm    Post subject: Reply with quote

Fitzcarraldo, I would just emerge wine-any so it's in world, and you don't need to worry about which combination will trigger the right dependency in the virtual.
It will satisfy the or-dep, as it's installed.
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1327
Location: United Kingdom

PostPosted: Thu Apr 13, 2017 4:42 pm    Post subject: Reply with quote

Thanks. I'm getting confused now! Are you saying that all I need to do is the following?:

1. Have only the following line in /etc/portage/package.use/wine:

Code:
app-emulation/wine-any abi_x86_32 -d3d9 -ldap -pipelight staging


2. Enter only the following command:

Code:
emerge app-emulation/wine-any virtual/wine

_________________
Clevo W230SS: amd64, OpenRC, nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64, OpenRC, xf86-video-ati, dual booting with Win 7 Pro 64-bit.
KDE on both laptops.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
steveL
Advocate
Advocate


Joined: 13 Sep 2006
Posts: 4809
Location: The Peanut Gallery

PostPosted: Fri Apr 14, 2017 4:13 pm    Post subject: Reply with quote

Pretty much, Fitzcarraldo, though I would just emerge -av app-emulation/wine-any on its own, first, so it is in world, then worry about the virtual which is likely a dependency of other things.

You may find you need a flag set on the virtual in order to satisfy those dependencies; I would set its flags to match wine-any (after you have wine-any safely installed with the flags you want) and then just let it get emerged automatically, or emerge -1av it.
Back to top
View user's profile Send private message
Linubie
Apprentice
Apprentice


Joined: 11 Jun 2004
Posts: 225

PostPosted: Sat Apr 15, 2017 10:04 am    Post subject: Reply with quote

Do these changes also apply to wine git "wine-9999"?

or can I keep my settings in

/etc/portage/package.keywords

Code:

=app-emulation/wine-9999 **

_________________
Mircosoft software is like having sex with a stranger, you always have to be careful not to get infected with something...
Back to top
View user's profile Send private message
Leio
Developer
Developer


Joined: 27 Feb 2003
Posts: 387
Location: Estonia

PostPosted: Sun Apr 16, 2017 7:09 am    Post subject: Reply with quote

I don't think from a quick skimming of the thread that this has been mentioned really yet, so:

By choosing to use wine-any, even if a specific patchset combination version via virtual/wine priority is sufficient, you will be getting updated versions slower than from e.g wine-vanilla or other specific patchset versions because the version update needs to wait for the patchset to actually be updated and in case of "any" also tested and made work all together.
_________________
GNOME team lead; GStreamer; MIPS/ARM64
Back to top
View user's profile Send private message
tld
Veteran
Veteran


Joined: 09 Dec 2003
Posts: 1221

PostPosted: Mon May 15, 2017 2:59 pm    Post subject: Reply with quote

Wow...maybe it's just me, but I have never been this confused by a news item or a change that I can recall. I'm currently just about up to date, and have the current stable app-emulation/wine-2.0 installed. What exactly is it that I'm supposed to be doing here to transition...and is it even necessary to do so? The news item keeps referencing the "old packaging" with the USE flags of "staging" and "d3d9" which don't seem to exist as USE flags in the old ebuild at all.

Clearly there's something fundamental I'm just missing here, but I might as well be trying to read something in Chinese. Thanks in advance for any explanation!

Tom
Back to top
View user's profile Send private message
NP-Hardass
Developer
Developer


Joined: 24 Mar 2013
Posts: 34

PostPosted: Wed May 17, 2017 6:33 am    Post subject: Reply with quote

Fitzcarraldo wrote:
Thanks. I'm getting confused now! Are you saying that all I need to do is the following?:

1. Have only the following line in /etc/portage/package.use/wine:

Code:
app-emulation/wine-any abi_x86_32 -d3d9 -ldap -pipelight staging


2. Enter only the following command:

Code:
emerge app-emulation/wine-any virtual/wine


Please see https://wiki.gentoo.org/wiki/Wine:_New_Packaging#Choosing_a_variant

Leio wrote:
I don't think from a quick skimming of the thread that this has been mentioned really yet, so:

By choosing to use wine-any, even if a specific patchset combination version via virtual/wine priority is sufficient, you will be getting updated versions slower than from e.g wine-vanilla or other specific patchset versions because the version update needs to wait for the patchset to actually be updated and in case of "any" also tested and made work all together.


Solid point. I included that in the new wiki entry for the sake of clarity.

tld wrote:
Wow...maybe it's just me, but I have never been this confused by a news item or a change that I can recall. I'm currently just about up to date, and have the current stable app-emulation/wine-2.0 installed. What exactly is it that I'm supposed to be doing here to transition...and is it even necessary to do so? The news item keeps referencing the "old packaging" with the USE flags of "staging" and "d3d9" which don't seem to exist as USE flags in the old ebuild at all.

Clearly there's something fundamental I'm just missing here, but I might as well be trying to read something in Chinese. Thanks in advance for any explanation!

Tom


See if this helps you out: https://wiki.gentoo.org/wiki/Wine:_New_Packaging
Back to top
View user's profile Send private message
tld
Veteran
Veteran


Joined: 09 Dec 2003
Posts: 1221

PostPosted: Wed May 17, 2017 1:33 pm    Post subject: Reply with quote

NP-Hardass wrote:
See if this helps you out: https://wiki.gentoo.org/wiki/Wine:_New_Packaging
Definitely. Thanks! So I take it that after the new packages are unmasked a basic upgrade to the new packaging will simply be:
Code:
emerge -aC app-emulation/wine
emerge -a virtual/wine

Is that correct? Thanks again!

Tom
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2038
Location: Illinois, USA

PostPosted: Wed May 17, 2017 2:36 pm    Post subject: Reply with quote

Moderator: Please split this if it is considered off-topic.


From the wiki article I gather that if I emerge virtual/wine then the variant is chosen is by the flags on virtual/wine and I will only have one variant installed.

So, if I want both wine-vanilla ans say wine-any(to experiment with), I should NOT emerge virtual/wine. Is that correct?

In any case, I should remove app-emulation/wine from /var/lib/portage/world. Is that correct?
Back to top
View user's profile Send private message
BobWya
Apprentice
Apprentice


Joined: 12 Aug 2012
Posts: 220
Location: Cambridge,UK

PostPosted: Wed May 17, 2017 3:23 pm    Post subject: Reply with quote

virtual/wine like all virtual/* 's allows other Gentoo packages to depend on the virtual package - rather than manually specifying all the alternatives, that the virtual package encompasses as dependencies...
These packages can be subject to change - which would make for a lot of churn in the Portage tree.

For example app-emulation/winetricks now has a run-time dependency on virtual/wine (ignoring the or condition):
Code:
RDEPEND="...
        || (
                app-emulation/wine
                virtual/wine
        )
        ..."

Rather than a direct runtime dependency on the new multislot app-emulation/wine-* packages

So knock yourself out... At the end of the day virtual/wine doesn't do much (as a package) except act as a placeholder. 8)

Bob
_________________
system: G751JT (ASUS-NotebookSKU); processor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz; memory: 32GiB System Memory; display: GM204M [GeForce GTX 970M]; disk: 2048GB Samsung SSD 850;BD-CMB UJ172 S;1024GB Samsung SSD 850
Back to top
View user's profile Send private message
NP-Hardass
Developer
Developer


Joined: 24 Mar 2013
Posts: 34

PostPosted: Wed May 17, 2017 9:59 pm    Post subject: Reply with quote

tld wrote:
NP-Hardass wrote:
See if this helps you out: https://wiki.gentoo.org/wiki/Wine:_New_Packaging
Definitely. Thanks! So I take it that after the new packages are unmasked a basic upgrade to the new packaging will simply be:
Code:
emerge -aC app-emulation/wine
emerge -a virtual/wine

Is that correct? Thanks again!

Tom


Correct.


Tony0945 wrote:
Moderator: Please split this if it is considered off-topic.


From the wiki article I gather that if I emerge virtual/wine then the variant is chosen is by the flags on virtual/wine and I will only have one variant installed.

So, if I want both wine-vanilla ans say wine-any(to experiment with), I should NOT emerge virtual/wine. Is that correct?

In any case, I should remove app-emulation/wine from /var/lib/portage/world. Is that correct?


You should probably emerge virtual/wine regardless, but yes, you'll need to put each variant in your world file since the virtual only ensures that one persists. For example, the vritual for editor will cause nano to be unmerged if you install vim, but you can keep both by manually adding nano to your world file.


BobWya wrote:
virtual/wine like all virtual/* 's allows other Gentoo packages to depend on the virtual package - rather than manually specifying all the alternatives, that the virtual package encompasses as dependencies...
These packages can be subject to change - which would make for a lot of churn in the Portage tree.

For example app-emulation/winetricks now has a run-time dependency on virtual/wine (ignoring the or condition):
Code:
RDEPEND="...
        || (
                app-emulation/wine
                virtual/wine
        )
        ..."

Rather than a direct runtime dependency on the new multislot app-emulation/wine-* packages

So knock yourself out... At the end of the day virtual/wine doesn't do much (as a package) except act as a placeholder. 8)

Bob


Well, placeholder and simple selector of a specific variant for those thank don't want to go overboard with tons of wine instances side by side (not that there's anything wrong with that :P).
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2038
Location: Illinois, USA

PostPosted: Wed May 17, 2017 10:01 pm    Post subject: Reply with quote

BobWya wrote:
So knock yourself out... At the end of the day virtual/wine doesn't do much (as a package) except act as a placeholder.
I emerged wine-vanilla and wine-any from your overlay (has priority over gentoo repo) Then I emerged eselect-wine (had to unmask it) and virtual/wine. First I unmerged app-emulation/wine.

Did the use flags on virtual/wine do anything? For vanilla and any, I just copied my old flags, although I guess two of them didn't matter?

EDIT:

I guess the virtual was also from your overlay.
Code:
X3 ~ # eix virtual/wine
[I] virtual/wine
     Available versions:  (~)0[1] [M](~)0-r4 {d3d9 staging}
     Installed versions:  0[1](08:37:27 PM 05/14/2017)
     Description:         Virtual for Wine that supports multiple variants and slotting

[1] "bobwya" /var/lib/layman/bobwya
Back to top
View user's profile Send private message
BobWya
Apprentice
Apprentice


Joined: 12 Aug 2012
Posts: 220
Location: Cambridge,UK

PostPosted: Wed May 17, 2017 10:34 pm    Post subject: Reply with quote

Tony0945 wrote:
BobWya wrote:
So knock yourself out... At the end of the day virtual/wine doesn't do much (as a package) except act as a placeholder.

I emerged wine-vanilla and wine-any from your overlay (has priority over gentoo repo) Then I emerged eselect-wine (had to unmask it) and virtual/wine. First I unmerged app-emulation/wine.

Did the use flags on virtual/wine do anything? For vanilla and any, I just copied my old flags, although I guess two of them didn't matter?

EDIT:

I guess the virtual was also from your overlay.
Code:
X3 ~ # eix virtual/wine
[I] virtual/wine
     Available versions:  (~)0[1] [M](~)0-r4 {d3d9 staging}
     Installed versions:  0[1](08:37:27 PM 05/14/2017)
     Description:         Virtual for Wine that supports multiple variants and slotting

[1] "bobwya" /var/lib/layman/bobwya


My Overlay only has 2 multislot wine variant packages: wine-vanilla (does not support Wine Staging) and wine-staging (forced Wine Staging).

I've hacked a system of multiversioning using the Gentoo _p suffix (package patch value). So you can say have multiple 9999 variants installed - all built against different Wine Git commits.
I've put in 10 symlinked 9999 versions in each of my 2 wine variant packages - just to get folk started...
This hack could not be used in the "official" Gentoo wine packages - because it, uhmmm ..., breaks a few packaging rules... 8)

I would recommend choosing either NP's Gentoo Portage tree wine packages or my Overlay packages - mixing and matching is not a good idea... :lol:

My virtual/wine package - has no USE flags... Like I said I view it as a placeholder that other packages can reference - to check that a Wine package is installed - to use as a run-time dependency.
OK - my virtual/wine version will pull in the (highest version) wine-vanilla package - if no wine variant packages are currently installed... But personally I just see that as a side effect.

To actually get wine installed (either from NP's packages in the main tree or my Overlay) I am using the system of:
Code:
emerge -v app-emulation/wine-staging:1.8

As an example - this will install the wine-staging variant version 1.8.
I might want to test this version for regressions or apply an out-dated patch, etc., etc.

Then if you want to make this currently active wine (if you have multiple multi-slot wine variant versions installed):
Code:
eselect wine set wine-staging-1.8


Edit (more advanced usage):
To apply patches selectively (to specific versions of a wine variant) I've got a system of directories now:
Code:
...
/etc/portage/patches/app-emulation/wine-staging:2.7
/etc/portage/patches/app-emulation/wine-staging:2.8

Some of these directories may just have symlinks back to a base patch version.

You can also have:
Code:
/etc/portage/patches/app-emulation/wine-staging

Which will contain globally applied patches (applied all versions of wine variant wine-staging).

My only problem now is running out of disk space - with all these Wine versions installed... I've had to move my Portage directory to another partition... Help!!
NP what are you doing to us!! :wink:

Bob
_________________
system: G751JT (ASUS-NotebookSKU); processor: Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz; memory: 32GiB System Memory; display: GM204M [GeForce GTX 970M]; disk: 2048GB Samsung SSD 850;BD-CMB UJ172 S;1024GB Samsung SSD 850
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 2038
Location: Illinois, USA

PostPosted: Wed May 17, 2017 11:24 pm    Post subject: Reply with quote

BobWya wrote:

My Overlay only has 2 multislot wine variant packages: wine-vanilla (does not support Wine Staging) and wine-staging (forced Wine Staging).


Of course you are correct and eix verifies it. However eix does report the flags on the virtual (see previous post) AND that the source is the bobwya overlay.
Perhaps a bug in eix.

Will unmerge wine-any and emerge wine-staging::bobwya as i want two variations, bone stock and enhanced to see if they make any difference.
Back to top
View user's profile Send private message
Chiitoo
Moderator
Moderator


Joined: 28 Feb 2010
Posts: 1399
Location: Here and Away Again

PostPosted: Thu May 18, 2017 2:21 pm    Post subject: ><)))°€ Reply with quote

Tony0945 wrote:
However eix does report the flags on the virtual (see previous post) AND that the source is the bobwya overlay.

Hmmm...

Tony0945 wrote:
Code:
X3 ~ # eix virtual/wine
[I] virtual/wine
     Available versions:  (~)0[1] [M](~)0-r4 {d3d9 staging}
     Installed versions:  0[1](08:37:27 PM 05/14/2017)
     Description:         Virtual for Wine that supports multiple variants and slotting

[1] "bobwya" /var/lib/layman/bobwya


Unless I'm missing something here, isn't the version with USE-flags there actually from Portage?

Moreover, your installed version doesn't show the flags, like so:

Code:
Installed versions:  0-r4{tbz2}[3](16:02:04 07/04/17)(-d3d9 -staging)

_________________
Kind Regards,
~ The Noob Unlimited ~

Sore wa sore, kore wa kore.
Back to top
View user's profile Send private message
gentoorockerfr
Tux's lil' helper
Tux's lil' helper


Joined: 25 May 2012
Posts: 142

PostPosted: Fri Aug 04, 2017 7:48 pm    Post subject: Reply with quote

I cannot install eselect-wine...it is strange.. i think that right words are in the package.keywords and use...


Code:
emerge --ask @preserved-rebuild

These are the packages that would be merged, in order:

Calculating dependencies... done!

!!! All ebuilds that could satisfy ">=app-eselect/eselect-wine-1.4" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-eselect/eselect-wine-1.4::bobwya (masked by: package.mask)
/usr/portage/profiles/package.mask:
# NP-Hardass <NP-Hardass@gentoo.org> (10 Apr 2017)
# Masked for testing


(dependency required by "app-emulation/wine-staging-2.12-r2::bobwya" [ebuild])
(dependency required by "@preserved-rebuild" [argument])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.


i have app-emulation/wine-staging-2.12-r2::bobwya in package.keywords and i have removed #(wine-*) in /usr/portage/profiles/package.mask
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Other Things Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum