On Sun, 09 Jan 2005, Brian Nelson wrote:
> On Sun, Jan 09, 2005 at 02:53:52PM -0800, Don Armstrong wrote:
> > The whole purpose of contrib (at least in my mind) is to indicate
> > to users that they will need something extra from non-free or even
> > something we can't distribute to make useful use
On Sun, Jan 09, 2005 at 02:53:52PM -0800, Don Armstrong wrote:
> On Sun, 09 Jan 2005, Brian Nelson wrote:
> > On Sun, Jan 09, 2005 at 12:59:08PM -0500, Glenn Maynard wrote:
> > > No more nonsensical than the fact that code within a program that
> > > makes optional use of a non-free library can go
This is a summary of the AM report for Week Ending 09 Jan 2005.
8 applicants became maintainers.
Christoph Haas
"I'm a 30 year old computer scientist who has been a Linux addict for
14 years. After I got told of Debian I switched to Debian in 2002 and
never looked back. I'm currently main
On Sun, 09 Jan 2005, Brian Nelson wrote:
> On Sun, Jan 09, 2005 at 12:59:08PM -0500, Glenn Maynard wrote:
> > No more nonsensical than the fact that code within a program that
> > makes optional use of a non-free library can go in main, while a
> > program consisting soley of that code must go in c
On Sun, Jan 09, 2005 at 03:28:43PM +0100, Martin Schulze wrote:
> Craig Sanders wrote:
> > this affects even DFSG-free drivers with DFSG-free patches. you often can't
> > apply the patches to the debianised kernel sources because the context that
> > the patch needs is missing.
> >
> > e.g. try d
On Sun, Jan 09, 2005 at 02:36:03AM +, Matthew Garrett wrote:
> It's becomingly increasingly common for hardware to require firmware to
> be loaded by the device driver on boot, rather than containing it in
> ROM. This is unfortunate, because in most cases the firmware is
> non-free. As a result
On Fri, Jan 07, 2005 at 03:05:33PM -0500, Glenn Maynard wrote:
> The GFDL is non-free, even without invariant sections. See:
>
> http://people.debian.org/~srivasta/Position_Statement.xhtml
>
> for a summary of a previous time this was discussed to death. :)
Thanks :-)
I feel a little embara
Andrew Suffield <[EMAIL PROTECTED]> wrote:
> On Sun, Jan 09, 2005 at 02:36:03AM +, Matthew Garrett wrote:
>> In the firmware case, the choice is rather different. At present, the
>> choice is not between free firmware or non-free firmware. The choice is
>> between non-free firmware on disk or n
On Sun, Jan 09, 2005 at 12:59:08PM -0500, Glenn Maynard wrote:
> On Sun, Jan 09, 2005 at 01:09:10AM -0800, Brian Nelson wrote:
> > It's also completely nonsensical that single drivers must go in contrib,
> > but a bundle of drivers may go in main as long as one of those drivers
> > does not use non
On Sun, Jan 09, 2005 at 02:36:03AM +, Matthew Garrett wrote:
> In the firmware case, the choice is rather different. At present, the
> choice is not between free firmware or non-free firmware. The choice is
> between non-free firmware on disk or non-free firmware in ROM. Putting
> drivers in co
On Sun, Jan 09, 2005 at 01:09:10AM -0800, Brian Nelson wrote:
> It's also completely nonsensical that single drivers must go in contrib,
> but a bundle of drivers may go in main as long as one of those drivers
> does not use non-free firmware.
No more nonsensical than the fact that code within a p
On Sun, Jan 09, 2005 at 03:21:40AM +, Matthew Garrett wrote:
> Steve Langasek <[EMAIL PROTECTED]> wrote:
>
> > I don't think I have a problem, conceptually, with a kernel package which
> > provides drivers for 10,000 different types of hardware, and needs to load
> > firmware from disk for 300
El dg 09 de 01 del 2005 a les 18:25 +0200, en/na Lars Wirzenius va
escriure:
> su, 2005-01-09 kello 16:52 +0100, Miguel Gea Milvaques kirjoitti:
> > Then if software as xpdf could be in main, software loading firmware
> > must be in main.
>
> Without commenting on the issue otherwise: This is not
Lars Wirzenius writes:
> su, 2005-01-09 kello 16:52 +0100, Miguel Gea Milvaques kirjoitti:
> > Then if software as xpdf could be in main, software loading firmware
> > must be in main.
>
> Without commenting on the issue otherwise: This is not a working
> analogy. xpdf can load any PDF file. Devi
su, 2005-01-09 kello 16:52 +0100, Miguel Gea Milvaques kirjoitti:
> Then if software as xpdf could be in main, software loading firmware
> must be in main.
Without commenting on the issue otherwise: This is not a working
analogy. xpdf can load any PDF file. Device drivers can, typically, only
load
Glenn Maynard wrote:
> On Sun, Jan 09, 2005 at 03:22:45PM +0100, Martin Schulze wrote:
> > The larger problem is to identify non-free blobs in the main kernel,
> > extract them into non-free and modify the driver so that it is able
> > to load the blob from a user provided location; and include thi
Craig Sanders wrote:
> this affects even DFSG-free drivers with DFSG-free patches. you often can't
> apply the patches to the debianised kernel sources because the context that
> the patch needs is missing.
>
> e.g. try downloading the patch[1] for DVICO Fusion DVB-T card's DFSG-free
> driver and
On Sun, Jan 09, 2005 at 03:22:45PM +0100, Martin Schulze wrote:
> The larger problem is to identify non-free blobs in the main kernel,
> extract them into non-free and modify the driver so that it is able
> to load the blob from a user provided location; and include this in
> our installer.
Isn't
Matthew Garrett wrote:
> Steve Langasek <[EMAIL PROTECTED]> wrote:
>
> > I don't think I have a problem, conceptually, with a kernel package which
> > provides drivers for 10,000 different types of hardware, and needs to load
> > firmware from disk for 300 of them, being in main (without a
> > Dep
Joey Hess <[EMAIL PROTECTED]> wrote:
> Matthew Garrett wrote:
>> In the firmware case, the choice is rather different. At present, the
>> choice is not between free firmware or non-free firmware. The choice is
>> between non-free firmware on disk or non-free firmware in ROM. Putting
>> drivers in c
Matthew Garrett wrote:
> In the firmware case, the choice is rather different. At present, the
> choice is not between free firmware or non-free firmware. The choice is
> between non-free firmware on disk or non-free firmware in ROM. Putting
> drivers in contrib penalises the former, and as a resul
On Sun, Jan 09, 2005 at 02:36:03AM +, Matthew Garrett wrote:
> In the firmware case, the choice is rather different. At present, the
> choice is not between free firmware or non-free firmware. The choice is
> between non-free firmware on disk or non-free firmware in ROM. Putting
> drivers in co
22 matches
Mail list logo
