Date: Fri, 07 Feb 2020 15:59:39 +0000
From: bugzilla-noreply@freebsd.org
To: ports-bugs@FreeBSD.org
Subject: [Bug 243957] emulators/i386-wine{-devel}: broken on CURRENT
Message-ID: <bug-243957-7788-D25PI6M3vA@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-243957-7788@https.bugs.freebsd.org/bugzilla/>
References: <bug-243957-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243957 --- Comment #5 from Lorenzo Salvadore <salvadore@freebsd.org> --- (In reply to Alex S from comment #4) What's specific to wine is that wine is broken on CURRENT. If a wine user wants to report that wine is broken on CURRENT, s/he might be tempted to open a PR about wine, although, as you observed, the problem is = more general. The role of this PR is to point to the general PR, in a similar ma= nner as what is usually done with complex exp-runs. Other ports broken for the same reason should, in my opinion, have similar = PRs that point to the general PR. Moreover, it is indeed likely that the general problem will be solved witho= ut modifications to the wine ports and that those ports will then work again untouched, but the opposite is not impossible: it is not impossible that wi= ne ports will need to change to integrate with the general solution. That said, if bugzilla triagers or committers agree with you and want to cl= ose this PR, I will not object. I am only trying to adopt the best strategy to = help people find existing bugs and understand the relations between them. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243957-7788-D25PI6M3vA>