ReaPack doesn't send back any tracking data (I'm generally against such practices in software). Its package repositories are decentralized so technically anyone hosting one could setup a server-side download counter. However falsifying the data would be easy.
As Mespotine said, some rarely installed package can be the perfect fit for someone's specific needs. They shouldn't be buried just because they don't appeal to a wide user-base.
I prefer to have ReaPack be neutral with each package being equal and instead improve searching (eg. last update adds support for REAPER-like synonyms).
Quote:
Originally Posted by Meo-Ada Mespotine
The idea of an update-counter is actually a good one. This could give the scripter a way to see, whether a script might need maintenance after some years. Though it should be enough as @modified_date in the script or something.
|
The package browser has an optional 'Last update' column (sortable). Not quite a counter or update score, but each package's history tab can give an idea of how often they're being updated (assuming the repository keeps old versions).