I think it is totally safe to delete this, because no user mentioned any use case where they would need 32-bit smbclient using wine on a 64-bit system. And no AUR wine packages are configured to build lib32 support for Samba. Therefore none of the existing wine builds would use lib32-smbclient even if they are coinstalled.
WINE has many legacy features, but if no one demands those, there is no point in providing them and maintaining unused packages. There are many other builds on AUR that really need expert maintainer attention. It is not worth the effort to waste it on something no application ever needs. @sl1pkn07, you might be preferring to be a completionist or to err on the theoretical extreme safe side when it comes to lib32 packages, but even you have not provided any existing use case for this one. On 10 September 2023 01:23:52 GMT+02:00, Fabian Maurer <dark.shad...@web.de> wrote: >On Samstag, 9. September 2023 21:00:49 CEST you wrote: >> El sáb, 9 sept 2023 a las 14:50, <not...@aur.archlinux.org> escribió: >> > DarkShadow44 [1] filed a deletion request for lib32-smbclient [2]: >> > >> > This is not needed anymore, the last packages that had this as >> > dependency (lib32-gnome-vfs) was deleted a while ago. >> > >> > [1] https://aur.archlinux.org/account/DarkShadow44/ >> > [2] https://aur.archlinux.org/pkgbase/lib32-smbclient/ >> >> needs for wine > >You're right, wine configure mentions missing support when that 32bit samba is >missing. Not sure what exactly it does though, it's not even optional for wine >and the wine tests pass even without the libs installed... > >FWIW, once the thunks work well enough, 32bit dependencies are going to be >obsolete anyways. Should we keep it around until then? > >Regards, >Fabian Maurer > >
