On 2023/04/26 12:11, bent...@openbsd.org wrote: > Nam Nguyen writes: > > Sorry about that. I imported it as is, so I will change to 0pl with > > EPOCH. > > No need for that. The 0pl suggestion (only a suggestion) was to avoid > hypothetical EPOCH in the future if upstream picks a version number less > than 1.0; but rolling back from 1.0 now that it's been committed would > mean a guaranteed EPOCH now. Stick with 1.0pl20230220 and no EPOCH.
Agreed (though 0plXX looks a bit odd to me and I'd probably go for 0.0.2023xxxx in that case) EPOCH isn't really a problem, the main thing (apart from ugly version numbers in PKGNAME) is that it can give some surprises with version specs in dependencies/@conflict lines/etc.
