hmm, distro wine package is pulling 64-bit and 32-bit packages. Can I have a 64-bit only wine...? Windows armhf programs are... rare. I don't expect to get much use from that.
hmm yeah, looks like I can remove wine32 and leave wine64 installed.
Never mind, that absolutely does not work. How frustrating.
Ok, looks like the trick is to remove wine32 WHILE LEAVING THE wine METAPACKAGE INSTALLED... despite pulling in wine32 you can apparently have it installed without 32. Nice.
wine will complain "it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"" but I'm just gonna ignore that, being able to run all 5 armhf Windows 8 programs is clearly not a useful feature.
Right, so I'm gonna do something really goofy and try to have my cake and eat it. I want 64-bit ARM wine running directly and either x86 or x64 (or both?) wine running in box86/64 both on my system... obviously they can't share the default prefix... so I'm gonna try to set up shell scripts to load the correct prefix for me when I want to run something.
This probably will not go well.
is it ~/bin I want to plop something like this into?
I'm pretty sure there's supposed to be a standard path for you to put programs within your home folder. I'd rather it be within my directory since these are my garbage scripts, rather they not pollute the rest of the system.
@onfy convention is to have ~/bin in PATH, debian does it by default
@noiob Weird, because this is my PATH:/home/sarah/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
@onfy yeah it gets applied on login, check your .profile
@noiob Yeah that did it (what does it say about me that I immediately guessed it...)
Good thing too, ~/.local/bin is apparently where pip puts stuff.
@noiob I created it just now, maybe I need to log out first.