[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: OpenBSD ports(7)
- Subject: Re: OpenBSD ports(7)
- From: James Turner <james@xxxxxxxxxxxxxxx>
- Date: Sun, 1 Jan 2017 22:05:48 -0500
- To: Ori Bernstein <ori@xxxxxxxxxxxxxx>
- Cc: myrddin-dev@xxxxxxxxxxxxxx
Semver sounds good to me. I can start the OpenBSD port at 0.1.0-alpha
and go up from there.
On Sun, Jan 01, 2017 at 06:54:42PM -0800, Ori Bernstein wrote:
> I was planning on just going with 0.1.0 for the first release, and more or
> less following semver after that.
>
> However, I don't particlularly care about versioning schemes. I also don't
> maintain much packaging. If there's something that makes life easier for you,
> I'd probably be willing to adopt it.
>
> On Sun, 1 Jan 2017 21:22:48 -0500, James Turner <james@xxxxxxxxxxxxxxx> wrote:
>
> > Hi,
> >
> > After reading the Myrddin Retrospective for 2016 I decided to put
> > together a port which can be added to the OpenBSD ports(7) system.
> >
> > I was going to wait for a stable release but remembered we now support
> > linking to arbitrary GitHub tags or commits. With that being said since
> > there aren't any tagged "releases" yet I need to come up with my own
> > versioning schema for the port. I was just going to use the date of the
> > commit, ie 20161229 but based on how the ports(7) system works when a
> > stable version comes out this version may be greater than the stable
> > version and may require setting an EPOCH forcing an extra v0 at the end
> > of the package name.
> >
> > I was wondering if you had any idea what the version of the first stable
> > release may look like so I could use a lower version number for these
> > GitHub based releases?
> >
> > Thanks.
> >
> > --
> > James Turner
> >
>
>
> --
> Ori Bernstein
>
--
James Turner