I just finished creating an ebuild for https://gitlab.com/brinkervii/grapejuice, but when I tried to launch it I realized it depends on having both /usr/bin/wine and /usr/bin/wine64 in the system. Currently eselect-wine only generates a link for /usr/bin/wine. I think it would make sense to update it to link the selected wine64 as well.
That link only exists because of binfmt needing a fixed path, otherwise it wouldn't be there either. Anything else should use the binaries from PATH rather than a fixed one.
From a quick look at the source, it seem to have a lot of detection methods and I don't think it should necessarily need it from /usr/bin -- not that I've tried it. Ideally I'd want to remove /usr/bin/wine given it's been messy to have, and not add more of it. If really needed adding wine64 is not entirely out of the question but I don't see why a python script can't find it in PATH (aka /etc/profile adds /etc/eselect/wine/bin to PATH which has wine64 and other binaries in it).
(In reply to Ionen Wolkens from comment #2) > From a quick look at the source, it seem to have a lot of detection methods > and I don't think it should necessarily need it from /usr/bin -- not that > I've tried it. > > Ideally I'd want to remove /usr/bin/wine given it's been messy to have, and > not add more of it. If really needed adding wine64 is not entirely out of > the question but I don't see why a python script can't find it in PATH (aka > /etc/profile adds /etc/eselect/wine/bin to PATH which has wine64 and other > binaries in it). Ah I didn't see that /etc/eselect/wine/bin was already in PATH since I checked from a root terminal. It is indeed there as my normal user so you are right this is an issue with the program not us. Thanks.
