hi, thanks for the answer. but i think i asked the question in the wrong way.
when i was testing out-of-date packages there were some with out-of-date flag before 2020 but those works i was meaning to ask, **how long does the package have to be out of sync with the main source ??** also i found some pkgs with depreciated `git://` but those works after modding it with `git+https://`. i generally report them if and only if they are orphans. On 11/13/23 04:51, aur-general-requ...@lists.archlinux.org wrote: > "David C. Rankin" <drankina...@gmail.com> writes: > >>> 2. should AUR host out-of-date but working packages ?? >>> >> >> There is always a sliding-scale of "How out-of-date?". Is some user of >> the package just flagging it 10 minutes after the latest upstream >> change? >> >> Is a dependency no longer supported by Arch (that's what AUR is >> for...)? >> >> Some packages may not have been updated in quite a while, but may be >> 100% valid and still good. >> >> This is hard to give advise on without knowing more about what you are >> considering "out-of-date"? > > I want to add that sometimes the maintainer might be already > working on an update but didn't release it. > It's easier to branch of a package and test it until merging it to the > AUR sometimes. -- yours zoorat, PGP: 00000586360F8791A5492251129802DDA8074345 GITHUB: https://github.com/z00rat
OpenPGP_signature.asc
Description: PGP signature
