Re: Switch fork, version going backward

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Fri, 28 Nov 2025 01:42:41 +0000
    From:        Emmanuel Dreyfus <manu%netbsd.org@localhost>
    Message-ID:  <aSj-EeFR6rXIGPJ_%homeworld.netbsd.org@localhost>


  | I tested switching from the former to the later with success, but there

Since this appears to more or less be your package, I'd say you can do
to it whatever makes it work best - though that would be clearer if you
first set MAINTAINER to yourself.

  | is a caveat: PKGNAME becomes openarc-1.3.0, which a is a lower version
  | number than openarc-20180921.
  |
  | How should that be dealt with?

I'd just make the PKGNAME become openarc-2025.1.3.0

that's "newer" than openarc-20180921 and also less than openarc-2025NNNN
for any digit N's, should there me a new release with the same old naming
structure (and you want to update to that).   If a real 1.0 appears,
and you want to switch to that, then  openarc-2026.1.0 would work (we're
near enough to 2026 for that not to matter).   And if it looks better to
just keep using the flowerysong versions, those can stay openarc-2025.X.Y.Z
forever - or update the "year" part as needed if after a switch to
openarc-2026.1.0 (or later) it seems better to revert to flowerysong again.

kre