kernel && patches

[Chuck Mead]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

nestu wrote:
| Hi everyone! ;)
| I wanted to ask if there is any policy about grabbing kernel source, if
| full source _must_ be DLed everytime.  I'm asking, 'cause when I bump up
| the kernel's version, I thought about patching it: maybe we could check
| for a base install  -say, for example, linux-XXX- and if it is there,
| get the patch to bump it up to  linux-XXX-yyy. Furthermore, IAC, the
| user can be prompted if he/she wants to fetch full source, or viceversa
| ( default is fetch the full source, but if a patch can be applied,
| prompt the user for what should be done).
| Another thing I thought of is kernel's config placement. How about
| putting a default location, and checking there first for it, and if it
| not there, prompt the user. Maybe this could be applied to more modules
| where a default_config could be saved in ${CONFIG_DIR} or something
| alike? Am I outdated on this? Pro/cons? What 'ya think ?
| C U,
| nestu ;)))

One rule of them for an Application Management System is that we not
require input from the user past the original call... now I know we
break that rule all over the place now but I would like us to minimize
the impact.

So far as patching goes I have no problem with it as there is no real
difference to th euser beyond shorter download time frames.

- --
csm
Lunar Project Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/NqnTq3bny/5+GAcRAjFkAJ43L0bOwX2XeYkX/Jgi6nmoNBg5VwCgkw/M
0ukKizNA8WmFb0s4bqB1dCY=
=4PAn
-----END PGP SIGNATURE-----