[Pkg-gridengine-devel] Future of gridengine in debian

Michael Banck mbanck at debian.org
Thu May 31 08:49:06 UTC 2012


Hi Dave,

On Wed, May 30, 2012 at 11:04:42PM +0100, Dave Love wrote:
> I've offered to try to help with this, but:
> 
> * I'm not a DD

That wouldn't be a problem at all.
 
> * It looks like substantial work just to understand how to do the
>   packaging (the framework for which seems to have changed substantially
>   since I last hacked on dpkgs) and there are currently patches I don't
>   understand.  (I adopted ones which I did understand and were useful.)
> 
> * Unfortunately our production system doesn't run Debian
> 
> * I don't know if Debian policy actually allows packaging it the way
>   it's typically run (from a shared installation) and it's not clear to
>   me that updates of a distributed system like this can be done reliably
>   in the normal Debian way
>
> I've always been interested in providing dpkg support anyway (preferably
> with no patches) as well as RPM, but haven't had time.  Is someone able
> to provide guidance on packaging (including Debian policy issues)?

Just installing everything under a common directory (like
/opt/gridengine) and then share this via e.g. NFS is indeed not OK with
Debian policy, so cannot be done for the official packages.

It would still be possible for somebody (I guess it only makes sense for
actual upstream projects) to provide 3rd party packages which just
install into that (or a different) directory.  In this case, the rest of
the Debian policy would not have to be followed by the letter either, as
long as it technically works fine. Updates could be done as usual.

However, I am not able to help with such a project on my free time right
now, I could probably review packaging work and give advice, though.

> Community Grid Engine:  http://arc.liv.ac.uk/SGE/

How is this fork different from the Open Grid Scheduler
(http://gridscheduler.sourceforge.net)?


Best regards,

Michael



More information about the Pkg-gridengine-devel mailing list