Date: Tue, 24 Mar 2020 13:29:30 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: "Dutchman01" <dutchman01@quicknet.nl> Cc: cy@FreeBSD.org, ports@FreeBSD.org Subject: Re: FreeBSD Port: nut-2.7.4_13 Message-ID: <202003242029.02OKTV4S011621@slippy.cwsent.com> In-Reply-To: <000001d60217$821d4cf0$8657e6d0$@quicknet.nl> References: <000001d60217$821d4cf0$8657e6d0$@quicknet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <000001d60217$821d4cf0$8657e6d0$@quicknet.nl>, "Dutchman01" writes: > This is a multipart message in MIME format. > > Is it an idea to switch NUT port so that it can use master sources from > https://github.com/networkupstools/nut for NUT port? > > > > Right now we are missing 3 years of upstream code improvements, updated and > new drivers and bug fixes. > > An newer release will not see soon its light. > > > > USE_GITHUB= yes > > GH_ACCOUNT= networkupstools > > GH_TAGNAME= e27f1f9 No and yes. No, we will not switch sysutils/nut to a devel port. However I have had for over a year now a partially completed nut-devel port in my git repo. It's on my list of things to finish. I just haven't managed to find the time to complete and test it. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202003242029.02OKTV4S011621>