General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Packages of netperf 2.6 and netperf-wrapper for Arch and Debian/Ubuntu
Date: Tue, 19 Mar 2013 10:26:09 -0700	[thread overview]
Message-ID: <51489FB1.7000104@hp.com> (raw)
In-Reply-To: <87fvzrxq8u.fsf@toke.dk>

On 03/19/2013 10:17 AM, Toke Høiland-Jørgensen wrote:
> Rick Jones <rick.jones2@hp.com> writes:
>
>> Ah yes, licensing - I guess netperf not being GPL would be an issue
>> there because the debian packaging scripts are themselves GPL?
>
> Yeah, I think they are by default. However, I looked at the 'copyright'
> file in the debian/ directory (which contains the packaging script), and
> couldn't find any reference to the license of the packaging files
> themselves; it only contained what appeared to be the list of copyrights
>  From netperf itself, with the name of the packager added on top.
>
> I suppose the safe thing to do would be to either (a) fire off an email
> to the packager and ask if he has any objections to his packaging being
> distributed as part of the netperf source, or (b) re-create the
> packaging script from scratch. As for (b), Debian does provide a set of
> scripts to scaffold the packaging scripts, so it might not be too hard
> to do. However, given that I am very much a Debian packaging novice,
> asking for permission to incorporate the existing packaging scripts
> might be worthwhile, at least as a first attempt.

I did send an email to the person I thought was the Debian mantainer - 
didn't get a response from him though.  Probably worth a second shot.

> What, btw, is the purpose of incorporating the packaging scripts? Do you
> want to provide ready-made .debs for download, or do you simply want to
> make it easier for others to create packages? And which distribution(s)
> are you planning to target?

The main reason is to make it easier for others to create packages, 
where others includes myself.

rick



      parent reply	other threads:[~2013-03-19 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18  2:38 Toke Høiland-Jørgensen
2013-03-18 17:34 ` Rick Jones
     [not found]   ` <87li9kzig6.fsf@toke.dk>
2013-03-18 19:56     ` Rick Jones
     [not found]       ` <87hak7zpzt.fsf@toke.dk>
2013-03-19 14:47         ` Rick Jones
     [not found]           ` <87vc8nxsbi.fsf@toke.dk>
2013-03-19 16:43             ` Rick Jones
     [not found]               ` <87mwtzxr4s.fsf@toke.dk>
2013-03-19 17:03                 ` Rick Jones
     [not found]                   ` <87fvzrxq8u.fsf@toke.dk>
2013-03-19 17:26                     ` Rick Jones [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=51489FB1.7000104@hp.com \
    --to=rick.jones2@hp.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox