anybody keen on doing a grid engin ebuild ? Reproducible: Always Steps to Reproduce: 1. 2. 3.
would be great if you could contribute an ebuild for sun grid engine. as i'm not very familiar it may be easier for you to build one and submit it.
I'll have a look into it when I get a chance :)
*** Bug 74411 has been marked as a duplicate of this bug. ***
news on this one?
Reopen if you have an ebuild. Meanwhile, marking LATER.
No, I do not have an ebuild, but I am thinking about writing one. This would be my first one, and I have some questions due to the complexity of this project. The installation is a little difficult because multiple hosts are involved. There is one or two master hosts, usually providing all common file hierarchy like /opt/sge ($SGE_ROOT) for all clients. Usually, the binaries are there, too, nothing needs to be local on the client nodes. But what if there are nodes of other architectures? Should the master host cross-compile binaries for them? Better not, huh? Or would one of those hosts emerge its binaries, and install them into the NFS-mounted tree? Or would we put the binaries out of the way (outside of /opt/sge), and every node emerges them for itself? We could split this into three ebuilds in sys-cluster: sge-base: init scripts and such sge-common: common stuff in /opt/sge sge-bin: binaries We could use use flags for this instead. The server use flag could activate features of sge-common, another one (which one?) would build binaries. What would make more sense? I think I would prefer use flags. Things that would be installed: sge-base: - An init script, starting the master daemon and/or execution daemon. The one I wrote also optionally mounts / unmounts $SGE_ROOT according to some settings in /etc/conf.d/sge. - An administration user (sgeadmin). Which ID should he get? It must be the same for all nodes to make things with NFS easier. - Path settings. There is also a little setup script which sets PATH, MANPATH, maybe a little more, but I think these settings should go into /etc/env.d/ directly. sge-common: - A lot of stuff in $SGE_ROOT. Installed only on master the host, other nodes mount it. sge-bin: - /opt/sge/bin/$arch, /opt/sge/utilbin/$arch, $opt/sge/lib/$arch with $arch being something like lx24-x86 or lx24-amd64. Other questions. I do not think there are source tarballs, but CVS access. What is the SRC_URI then? Do I checkout from CVS, create a tar ball and upload to a distfiles mirror? That's my thoughts so far. I have very little experience with SGE yet, and I do not know if I would find the time soon to create an ebuild, so don't expect too much. But it would be an interesting project, and it would be cool if portage could provide SGE.
