[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Devices and patches



What program are you talking about? 

> The program needs a patch to be applied to the kernel... How can you mark
> this need in the package ? Should it be automatized? 

It's a patch not included with the standard kernel source?  I don't know
if there's an official policy on what to do with these;  I *think* that
sometimes there's just a note in the package description saying that
"You'll have to apply this patch <list patch URL here> for this program to
work".  It almost certainly should _not_ be automated -- you don't want to
play around with somebody else's kernel setup.

> My second question: This program needs to create a device to run... Where
> do I create it? Should it be included in MAKEDEV ?

Read http://www.debian.org/doc/debian-policy/ch4.html#s4.6;  here's an
excerpt:

"If a package needs any special device files that are not included in the
base system, it has to call makedev in the postinst script, after asking
the user for permission to do so."

                     					Will

--------------------------------------------------------------------------
|   harpo@udel.edu lowe@cis.udel.edu lowe@debian.org lowe@asel.udel.edu  |
|			http://www.cis.udel.edu/~lowe/		         |
|    PGP Public Key:  http://www.cis.udel.edu/~lowe/index.html#pgpkey    |
--------------------------------------------------------------------------



Reply to: