From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aron Xu <aron@debian.org>
Subject: Re: netcat-openbsd implementations
Date: Tue, 27 Dec 2016 12:41:44 +0800
Message-ID: <CAMr=8w6OiKQ2Mo+dMrXjonw-6FR_jAFmsYWH6axHV4drAJ__TQ@mail.gmail.com>
References: <87d1n0fb1c.fsf@we.make.ritual.n0.is>
	<CAMr=8w5msWELQP_RzMoXOhzw7_-ub3UbW7qFUgn6Dqbdr4qg3w@mail.gmail.com>
	<87wpkxzrlr.fsf@we.make.ritual.n0.is> <87wpkrjjs0.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50781)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <happyaron.xu@gmail.com>) id 1cLjaU-000184-GX
	for guix-devel@gnu.org; Mon, 26 Dec 2016 23:42:11 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <happyaron.xu@gmail.com>) id 1cLjaT-0004eg-HV
	for guix-devel@gnu.org; Mon, 26 Dec 2016 23:42:10 -0500
In-Reply-To: <87wpkrjjs0.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org, ng0 <ng0@we.make.ritual.n0.is>

Hi there,

On Tue, Jul 12, 2016 at 5:19 PM, Ludovic Court=C3=A8s <ludo@gnu.org> wrote:
> Hi,
>
> ng0 <ng0@we.make.ritual.n0.is> 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 containing
> 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, ng0=
.
>
> Ludo=E2=80=99.

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