tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: okteta



* On 2023-08-20 at 22:15 BST, David Brownlee wrote:

On Sun, 20 Aug 2023 at 19:38, Joerg Sonnenberger <joerg%bec.de@localhost> wrote:

On Sun, Aug 20, 2023 at 12:35:52PM -0400, Greg Troxel wrote:
> I think it's a simple matter of someone producing a patch for epoch.  I
> am not aware of any real objections to doing this in a way with
> semantics that match the other systems.

That's not the reason. The reason we don't have epoch numbes is because
the existing system handles the case well enough. There is just no
generally agreed standard on what to use as magic high component number.

I would have to disagree there - the issue of an upstream version
reducing is rare, but we do not have any way to handle it, and have
this issue _every_ time.

What actually needs to be handled? FWIW pkgin will simply pull in the "newer" package, even if the version goes backwards (like we had recently with some ruby package that got reverted).

--
Jonathan Perkin   -   mnx.io   -   pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com


Home | Main Index | Thread Index | Old Index