linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kel Modderman <kel@otaku42.de>
To: debian-devel@lists.debian.org
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Tim Gardner <tim.gardner@canonical.com>
Subject: Re: [renamed] Debian crda?
Date: Thu, 26 Mar 2009 03:37:37 +1000	[thread overview]
Message-ID: <200903260337.37783.kel@otaku42.de> (raw)
In-Reply-To: <43e72e890903250051j44955276j42fce045c5079b87@mail.gmail.com>

On Wednesday 25 March 2009 17:51:41 Luis R. Rodriguez wrote:
> On Wed, Mar 25, 2009 at 12:47 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> > On Wed, Mar 25, 2009 at 12:39 AM, Paul Wise <pabs@debian.org> wrote:
> >> On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> >>
> >>> Last time I poked them it seemed it was not easy to figure out how to
> >>> deal with, if at all, the optional but recommended RSA signature stuff
> >>> [1] with the DFSG.
> >>>
> >>> [1] http://wireless.kernel.org/en/developers/Regulatory#RSADigitalSignature
> >>
> >> What is the percieved DFSG/RSA conflict? I can't detect any based on
> >> that section of the page.
> >
> > Thanks Paul, then its just a matter of packaging. There is an
> > debian-example/ directory with a cdbs example of how to package for
> > wireless-regdb and crda if anyone is up for it.

The example packaging needs some love, I think. I don't see it as a great
reference to the eventual packaging material that would enter Debian.

> 
> And as its probably best to coordinate with Ubuntu, they have a
> wireless-crda package which combines both into one package. Its
> shipping for Jaunty.

And that's the only way to sanely package it (by combining the two pieces
upstream splits) as show by Fedora also choosing that route.

Luis why can't CRDA and regd simply be released in same tarball considering
they have such a strong relationship with eachother due to the openssl stuff?

Thanks, Kel.

  parent reply	other threads:[~2009-03-25 17:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  7:09 [renamed] Debian crda? Luis R. Rodriguez
     [not found] ` <e13a36b30903250039h55c8a01cg9dada9256bc8b1ae@mail.gmail.com>
2009-03-25  7:47   ` Luis R. Rodriguez
2009-03-25  7:51     ` Luis R. Rodriguez
2009-03-25 11:34       ` Evgeni Golov
2009-03-25 17:37       ` Kel Modderman [this message]
2009-03-25 17:40         ` Johannes Berg
2009-03-25 17:41         ` Luis R. Rodriguez
2009-03-25 18:42           ` Kel Modderman
     [not found]             ` <e13a36b30903251203v7c53fb20g64bf61e4e433377@mail.gmail.com>
2009-03-25 20:25               ` Luis R. Rodriguez
2009-03-25 20:27                 ` Luis R. Rodriguez
     [not found]               ` <e13a36b30903252008i72caad77y32e31f625b7cb842@mail.gmail.com>
2009-03-26  4:19                 ` Luis R. Rodriguez
2009-03-26  4:59                   ` Paul Wise
2009-03-27  4:00                     ` Luis R. Rodriguez
2009-03-25 17:45   ` Kel Modderman
2009-03-25 18:12     ` John W. Linville

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=200903260337.37783.kel@otaku42.de \
    --to=kel@otaku42.de \
    --cc=debian-devel@lists.debian.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=tim.gardner@canonical.com \
    /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;
as well as URLs for NNTP newsgroup(s).