Hi, Yes, the upstream did not made up a release in recent years, but keeps taking up new commits to the code, and if you want to get these commits with the recent old release, you should define a github tagname to the newest commit of the repository, and i guess it's advised to add snapshot date to version in this case.
I didn't contact with upstream. Thanks. Kind regards, Yusuf Yaman. Sent with Proton Mail secure email. On Monday, September 15th, 2025 at 9:45 PM, Patrick M. Hausen <[email protected]> wrote: > Hi, > > > Am 15.09.2025 um 20:17 schrieb Yusuf Yaman [email protected]: > > I am using repology.org for a while because it is useful, but, in my > > maintainer information page, this port is seen as problematic because it > > has the "release date" on ${DISTVERSION} too. > > > > Just curious because I do a bit of porting myself every now and then. > > Is that necessary because upstream has not tagged a new release since 2015 and > is this the only way to pick up the later changes? Or the commonly recommended > one for the ports system? > > And then of course I wonder why there is no new release. The much more > prominent > NUT (Network UPS Tools) suffered from the same - no release, so no updated > port/package. > > Did you contact upstream? > > Kind regards, thanks in advance if you take the time, > Patrick > -- > punkt.de GmbH > Patrick M. Hausen > .infrastructure > > Sophienstr. 187 > 76185 Karlsruhe > > Tel. +49 721 9109500 > > https://infrastructure.punkt.de > [email protected] > > AG Mannheim 108285 > Geschäftsführer: Daniel Lienert, Fabian Stein
