Jason Azze via devel :
> I predict that ESR will ask me for an alternative approach. He won't
> like my recommendation. It's to use a feature or development branch
> for a change as big as the introduction of NTS.
Even if I liked using feature branches (and I don't; see
https://blog.ntpsec.org/20
On Thu, Feb 14, 2019, at 12:56 PM, Eric S. Raymond via devel wrote:
> I've added a mandatory waf check for the libaes_siv library.
[snip]
> At some point it will probably be taken into OpenSSL and this separate
> dependency will go away.
Hmmm. I certainly understand why this is necessary to mov
Daniel Franke :
> Release tags match v.., so just check the tag list for
> the most recent v1.y.z. Don't automatically go to 2.anything since releases
> are semantically versioned and that would indicate backward-incompatibility.
That's going to be a pain to implement and debug in the CI context.
On Thu, Feb 14, 2019, 2:24 PM Eric S. Raymond via devel Daniel Franke :
> > You probably don't want to auto-pull the latest HEAD every time it gets
> an
> > update; only releases get the full battery of QA. Note I'll probably be
> > stamping a release this weekend since the last release from two y
Release tags match v.., so just check the tag list for
the most recent v1.y.z. Don't automatically go to 2.anything since releases
are semantically versioned and that would indicate backward-incompatibility.
On Thu, Feb 14, 2019, 17:24 Eric S. Raymond Daniel Franke :
> > You probably don't want t
Daniel Franke :
> You probably don't want to auto-pull the latest HEAD every time it gets an
> update; only releases get the full battery of QA. Note I'll probably be
> stamping a release this weekend since the last release from two years ago
> has a build issue with more recent OpenSSL versions.
You probably don't want to auto-pull the latest HEAD every time it gets an
update; only releases get the full battery of QA. Note I'll probably be
stamping a release this weekend since the last release from two years ago
has a build issue with more recent OpenSSL versions.
On Thu, Feb 14, 2019, 17
Hal Murray :
> Did you fix the CI checks?
>
> Is anybody working on fixing libeas_siv to build on NetBSD? Until that is
> fixed, we won't build on NetBSD.
Yikes! I forgot about the CI - I almost never have to modify it.
Matt Selsky maintains that YAML file. I've pinged him on IRC. We';ll
fig
> I've added a mandatory waf check for the libaes_siv library.
Thanks.
Did you fix the CI checks?
Is anybody working on fixing libeas_siv to build on NetBSD? Until that is
fixed, we won't build on NetBSD.
--
These are my opinions. I hate spam.
I've added a mandatory waf check for the libaes_siv library.
The requirement for it has been document it in INSTALL for some time;
it's required for the NTS Support we're developing.
We didn't source-include it because Daniel wants his cmake build to
keep control of the compilation environment for
10 matches
Mail list logo
