Previously, you flagged this package as out-of-date, just because you wanted me to change the dependency from 'megasync-bin' to 'megasync'. And now requesting to orphan this package?
I believe this package should continue to use 'megasync-bin' to match the name itself, which is 'thunar-megasync-bin', and both binaries come from the same URL source. And the reason I wanna keep the binary package is because me myself, whenever I'm installing any AUR packages, I prefer to choose the prebuilt binary version so that I don't have to wait for the compiling process. May I suggest you create a new AUR package, 'thunar-megasync', since you requested the previous one to be deleted? Reference: https://lists.archlinux.org/hyperkitty/list/aur-requests@lists.archlinux.org/message/S7ALZ727ZWBPRENLPYIDXGWVKGHRPPEV/ This way, users are able to choose either to grab the prebuilt binary or use the other one instead. Cheers! On Tue, Feb 27, 2024 at 6:30 AM <not...@aur.archlinux.org> wrote: > MarsSeed [1] filed an orphan request for thunar-megasync-bin [2]: > > Needs update. Maintainer seems to be inactive. > > Last updated: 2021-03-31. > Flagged out-of-date: 2024-01-23. > > [1] https://aur.archlinux.org/account/MarsSeed/ > [2] https://aur.archlinux.org/pkgbase/thunar-megasync-bin/
