all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org, Aron Xu <aron@debian.org>
Subject: Re: netcat-openbsd implementations
Date: Tue, 12 Jul 2016 11:19:27 +0200	[thread overview]
Message-ID: <87wpkrjjs0.fsf@gnu.org> (raw)
In-Reply-To: <87wpkxzrlr.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's message of "Thu, 07 Jul 2016 10:10:08 +0000")

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

  reply	other threads:[~2016-07-12  9:19 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 [this message]
2016-12-27  4:41       ` Aron Xu
2016-12-27  9:42         ` ng0
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=87wpkrjjs0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=aron@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.