all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: Aron Xu <aron@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: netcat-openbsd implementations
Date: Tue, 27 Dec 2016 09:42:03 +0000	[thread overview]
Message-ID: <87inq57lp0.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAMr=8w6OiKQ2Mo+dMrXjonw-6FR_jAFmsYWH6axHV4drAJ__TQ@mail.gmail.com>

Hi Aron,

Aron Xu <aron@debian.org> writes:

> Hi there,
>
> On Tue, Jul 12, 2016 at 5:19 PM, Ludovic Courtès <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’s not an option then yes, you can do as you proposed, ng0.
>>
>> Ludo’.

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 containing
   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.

Thanks,
-- 
♥Ⓐ  ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org

  reply	other threads:[~2016-12-27  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 12:13 netcat-openbsd implementations ng0
2016-07-03  9:52 ` Aron Xu
2016-07-07 10:10   ` ng0
2016-07-12  9:19     ` Ludovic Courtès
2016-12-27  4:41       ` Aron Xu
2016-12-27  9:42         ` ng0 [this message]
2016-12-27 10:30           ` Aron Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inq57lp0.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@libertad.pw \
    --cc=aron@debian.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.