Re: OpenBSD ports(7)
[Thread Prev] | [Thread Next]
- Subject: Re: OpenBSD ports(7)
- From: Ori Bernstein <ori@xxxxxxxxxxxxxx>
- Date: Tue, 7 Feb 2017 21:53:08 -0800
- To: James Turner <james@xxxxxxxxxxxxxxx>
- Cc: myrddin-dev@xxxxxxxxxxxxxx
Merged. On Tue, 7 Feb 2017 18:55:56 -0500, James Turner <james@xxxxxxxxxxxxxxx> wrote: > Pull request just sent on Github. > > James > > On Tue, Feb 07, 2017 at 02:14:27PM -0500, James Turner wrote: > > Will do. Expect a patch and/or pull request on Github soonish. > > > > James > > > > On Tue, Feb 07, 2017 at 12:33:23AM -0800, Ori Bernstein wrote: > > > So, as I'm writing up the docs and preparing for a release, I took a peek at > > > the port, and noticed you have a couple of patches; if you want to upstream > > > them, I'd love to pull them back in. > > > > > > Doing the right thing out of the box is something I'd like to aim for on all > > > the OSes I support. > > > > > > On Sun, 1 Jan 2017 22:05:48 -0500, James Turner <james@xxxxxxxxxxxxxxx> wrote: > > > > > > > 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 > > > > > > > > > > > > > -- > > > Ori Bernstein > > > > > > > -- > > James Turner > > > > -- > James Turner > -- Ori Bernstein
Re: OpenBSD ports(7) | Ori Bernstein <ori@xxxxxxxxxxxxxx> |
Re: OpenBSD ports(7) | James Turner <james@xxxxxxxxxxxxxxx> |
Re: OpenBSD ports(7) | James Turner <james@xxxxxxxxxxxxxxx> |
- Prev by Date: Re: OpenBSD ports(7)
- Next by Date: libjson: merged into standard distribution.
- Previous by thread: Re: OpenBSD ports(7)
- Next by thread: libjson: merged into standard distribution.
- Index(es):