On Apr 21, 2020, at 3:28 AM, Stelios Tsampas via aur-requests <aur-requests@archlinux.org> wrote:
Are you suggesting that this package maintain a fork of the library which still supports winelib builds? Or instead that it continue to exist to build and install this old commit which will quickly become obsolete as further improvements are added past this commit?On 4/21/20 11:53 AM, notify@aur.archlinux.org wrote:
soredake [1] filed a deletion request for dxvk-winelib [2]: https://github.com/doitsujin/dxvk/commit/436357e28096f5e1e25aa8b72fceb77123ea8404 [1] https://aur.archlinux.org/account/soredake/ [2] https://aur.archlinux.org/pkgbase/dxvk-winelib/The version pointed by the tag still builds correctly under wine. The commit you are pointing to
is after the tag built by this package. And even so, since this package builds correctly for this version,
what is the problem with it existing? Why should this be deleted?