svn commit: r510920 - in head/sysutils: . syslog-ng syslog-ng323

[Cy Schubert]

In message <5D82F790-497B-46DB-8819-54BE2FC0C9E9 at adamw.org>, Adam 
Weinberger wr
ites:
> > On Sep 3, 2019, at 05:29, Cy Schubert <Cy.Schubert at cschubert.com> wrote:
> > 
> > In message <201909031118.x83BIUTl031197 at slippy.cwsent.com>, Cy Schubert 
> > writes:
> >> In message <20190903082020.73tdsn7gio7svyfm at ivaldir.net>, Baptiste 
> >> Daroussin wr
> >> ites:
> >>>> On Tue, Sep 03, 2019 at 03:31:57AM +0000, Cy Schubert wrote:
> >>>> Author: cy
> >>>> Date: Tue Sep  3 03:31:56 2019
> >>>> New Revision: 510920
> >>>> URL: https://svnweb.freebsd.org/changeset/ports/510920
> >>>> =20
> >>>> Log:
> >>>> Thank you to Peter Czanik, of Balabit the producers of syslog-ng, for
> >>>> a port of the new syslog-ng 3.23 branch. This is 3.23.1.
> >>>> =20
> >>>> Submitted by:    Peter Czanik (CzP) <peter.czanik at oneidentity.com>
> >>>>         Balabit (a OneIdentity company) / syslog-ng upstream
> >>> 
> >>> Do we really need all possible revision of syslog-ng in ports?
> >>> 
> >>> Do they have that many incompatibilities between each others that is it
> >>> mandatory to have all the supported one? isn't it possible to only live w
> it
> >> =
> >>> h the
> >>> lastest stable version? it seems most linux distribution are doing that a
> nd
> >>> happy with it, so does pkgsrc and openbsd ports.
> >>> 
> >>> I think it is more confusing users than it does help them to have 15 diff
> er
> >> =
> >>> ent
> >>> version of syslog-ng in ports.
> >> 
> >> No we don't. I periodically cull older ones following consultation with ou
> r 
> >> upstream. It's probably time to do that again.
> > 
> > I've pinged our upstream for his input. We'll have a plan by the end of the
>  
> > week.
>
> Has this been resolved? I saw that you purged unsupported versions, but is th
> ere a need for every supported version to be in ports?

Yes. Peter suggested we keep the last four major releases of which #4 
expires half a year after the most recent major release is released. Minor 
releases of course don't cause added ports.

Having said that, Peter Czanik, the who is employed by the upstream 
corporation who supplies the ports to us usually waits until a .1 minor 
release. Peter works for Balabit as the packager of FreeBSD ports and some 
Linux distro packages. He's quite conservative in that he prefers not to 
have us update the meta-port if he feels the latest isn't to his thinking 
"stable enough."

The last I heard from him was that he wanted to check with the Linux 
distros he supported to find common ground that we all do the same or 
similar.

In the mean time I do have some deprecations/expirations in my git repo. I 
should commit commit them as this has been sitting in my git repo for a 
couple of weeks.


-- 
Cheers,
Cy Schubert <Cy.Schubert at cschubert.com>
FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.