From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aron Xu Subject: Re: netcat-openbsd implementations Date: Tue, 27 Dec 2016 18:30:31 +0800 Message-ID: References: <87d1n0fb1c.fsf@we.make.ritual.n0.is> <87wpkxzrlr.fsf@we.make.ritual.n0.is> <87wpkrjjs0.fsf@gnu.org> <87inq57lp0.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47146) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cLp1z-0005BU-HV for guix-devel@gnu.org; Tue, 27 Dec 2016 05:30:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cLp1y-0007L8-Fx for guix-devel@gnu.org; Tue, 27 Dec 2016 05:30:55 -0500 In-Reply-To: <87inq57lp0.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: ng0 Cc: guix-devel@gnu.org On Tue, Dec 27, 2016 at 5:42 PM, ng0 wrote: > Hi Aron, > > Aron Xu writes: > >> Hi there, >> >> On Tue, Jul 12, 2016 at 5:19 PM, Ludovic Court=C3=A8s wro= te: >>> Hi, >>> >>> ng0 skribis: >>> >>>> Aron Xu writes: >>> >>> [...] >>> >>>>> I don't treat this netcat-openbsd a full fork even if it's targeting >>>>> an older revision at the moment. Also, maintaining patches are very >>>>> easy using the git-buildpackage[1] tools for Debian packages. >>>>> >>>>> [1]https://wiki.debian.org/PackagingWithGit >>>>> >>>>>> >>>>>> Third option I thought of, could Debian provide a tarball of >>>>>> the orig-source with the patches applied, so there's no need >>>>>> to conflict with systems currently pulling one or both of the >>>>>> currently existing tarball. >>>>>> >>>>> >>>>> I think it is hardly possible to provide another tarball because >>>>> there's no way of doing that with current Debian infrastructure. But >>> >>> [...] >>> >>>> So what do others make of this? >>>> Ludovic, any follow-up thoughts or actions regarding our thread >>>> on this? >>> >>> I think it would be more convenient to have a source repo for >>> netcat-openbsd rather than the current setup with a set of >>> debian/*.patch files. >>> >>> Perhaps alioth.debian.org could host a netcat-openbsd project containin= g >>> the GNU/Linux port (with all the patches applied), from which both the >>> Debian package and the Guix package would be built? >>> >>> If that=E2=80=99s not an option then yes, you can do as you proposed, n= g0. >>> >>> Ludo=E2=80=99. > > To me it still looks like the layout and releases did not include > any of the listed above, so if I'll package openbsd-netcat with > patches in the source sometime next year. > >> We've updated netcat-openbsd package to 1.130 with all patches >> refreshed, if you have plan to follow the update then it's the time, >> :) >> >> Cheers, >> Aron > > Thanks for your message on the update. So far the package on our > (my) side is stuck in the TODO phase of applying the patches as > it's not a priority for me. > > I have no idea about the Debian project organization, but > if it's not already an open bug, could you open a bug for your > infrastructure and/or openbsd-netcat about what Ludovic wrote > here: > > > > Perhaps alioth.debian.org could host a netcat-openbsd project containi= ng > the GNU/Linux port (with all the patches applied), from which both the > Debian package and the Guix package would be built? > > > > This would make work on our side (and possibly also other systems > distributing your version of netcat) much easier, otherwise I'll > just pull in the patches. > I've said before that I don't treat it as a fork, so sorry I'm not going to request that feature on Debian's infrastructure. Thanks, Aron