default_python_build and initrd detection patches

[Jannis Pohlmann]

Hey guys,

I don't know exactly who has commit access for
http://svn.foo-projects.org/svn/lunar/lunar/, but here are two patches
for you to consider.

1. lunar-default_python_build.patch -- We have a lot of python modules
   which all share the same build instructions:

     python setup.py config && 
     prepare_install && 
     python setup.py install

   The attached patch introduces default_python_build(). If there is an
   executable ./configure script or no setup.py, it falls back to
   default_build. Otherwise it runs

     python setup.py build && 
     prepare_install &&
     python setup.py install

   It uses "setup.py build" instead of "setup.py config" because the
   config command doesn't always seem to be available.

2. lunar-initd-detection.patch -- This is a patch for the initd.plugin.
   It currently uses the expression '# chkconfig: ' to detect init
   scripts. However, there is no need to use spaces in the expression,
   especially not after the 'chkconfig:'. Perl-style regular expressions
   in grep are a POSIX extension, so '\t' won't work here. Thus, the
   patch changes '# chkconfig: ' to '^# chkconfig:' which improves
   things a bit.

Cheers,
Jannis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lunar-default-python-build.patch
Type: text/x-patch
Size: 627 bytes
Desc: not available
URL: <http://foo-projects.org/pipermail/lunar-dev/attachments/20090315/a2727033/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lunar-initd-detection.patch
Type: text/x-patch
Size: 1516 bytes
Desc: not available
URL: <http://foo-projects.org/pipermail/lunar-dev/attachments/20090315/a2727033/attachment-0001.bin>