- User Since
- Aug 14 2018, 8:24 PM (94 w, 1 d)
Dec 13 2019
Dec 11 2019
Well, assuming Phabricator notifications are not broken and this is indeed intentional silence, as an alternative "solution" I can only recommend making (as an option or a slave package) i386-wine-devel coinstallable with wine-devel by stripping all conflicting files from i386-wine-devel. That should enable wow64 functionality while preserving every single annoyance about the current system.
Dec 5 2019
@mat Ok, pretty please with a direct mention on top. Specifically, since dbn@ has essentially abandoned this patch, what should we do with it? Does it make sense for me to resubmit an updated patch? (It's quite a bit larger, though.) Who is actually supposed to review, commit or decline this?
Oct 13 2019
As a reminder to new subscribers, just to make sure we are on the same page: this review is dead. Period.
Sep 16 2019
Aug 26 2019
Regarding the recent bug tracker comment, I would actually appreciate this and https://reviews.freebsd.org/D14721 being closed. Right now for people glancing through this thread it's not clear that nothing here is being actively worked on. @dbn?
Jul 28 2019
Jul 24 2019
Should be in reasonable shape now.
Jul 20 2019
Jul 19 2019
Oh, hello Theron.
Jun 19 2019
Ok, this looks as good as dead. Was this proposal discussed elsewhere and put on hold? Anything else?
Jan 18 2019
Any plans on doing something with this in 2019?
Nov 7 2018
Oh, nice. I immediately got flamed for mentioning that version discrepancy on the FreeBSD forums (with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189180 closed as a consequence), so this patch is extremely welcome.
Oct 9 2018
Sep 2 2018
@rozhuk.im-gmail.com You know the chroot approach is basically unmergable, right? Unless D16830: USES=lib32: add support for lib32- companion ports also fails review for some reason, it will not be used.
Aug 22 2018
I've also made an attempt to modify some ports according to the initial variant of this patch (i.e., flavors). I will update my diff in a few days, but where exactly should I put proposed additions and/or changes? Not clear on the workflow.
Ok, this looks quite neat.
Aug 21 2018
I am realizing that to resolve the need for i386-on-amd64 packages properly would require much cooperation, making this a large undertaking, as it was for the adoption of FLAVORS.
In the interest of improving Wine experience on FreeBSD for all, it is probably better to avoid such potentially controversial changes and to keep to the model of distributing all i386 Wine libs as a single package, despite the many drawbacks.