Hi, I've made a first attempt at a systemimager server ebuild, for mass installation of installed machines. The ebuild installs and uninstalls correctly on my machine, but I think is probably underdefined in terms of the dependencies; - I'm not sure as to the best way to carry this through, so some advice would be appreciated. I am quite happy to work to improve this further, so constructive comments on how to go about improving things would be appreciated.. I would suggest sys-cluster/systemimager as the category. thanks Lindsay
Created attachment 44454 [details] an ebuild for installing the systemimager server on a sytem this is an initial version of the ebuild. This is also my first ebuild, so there may well be some naive mistakes. Comments to improve this would be appreciated.
Ok the small list - I haven't tried installing it. eutils isn't used so that line can be removed DESCRIPTION describes the program not the ebuild SRC_URI - if using a common mirror like sourceforge use mirror://sourceforge/${PN}/${P}.tar.bz2 or similar. With dependancies - list what is required to compile the program and what is required to run it. Then associate those programs and libraries to packages. (qpkg -f -v /path/to/file). Chances are there won't be too may for this (I could be wrong) see if emake can be used instead of make. This will incorportate user setting like paralell make settings.
This should probably go in app-admin where the old systemimager stuff was. See http://www.gentoo.org/cgi-bin/viewcvs.cgi/app-admin/. It's worth seeing what the (former) maintainer thinks about this, too.
Created attachment 44546 [details] A revised ebuild file, modified with regard to the comments by dragonheart@gentoo.org I've made some changes inline with the comments raised yesterday; note that this ebuild builds from source, rather than using the rpms released by the systemimager team (which the original ebuild used). The reason for the large number of dependencies is that the tarball contains a number of packages like e2fsprogs, reiserfsprogs, etc, which are compiled in order to build an install cd image for imaging the clients. I'm not sure what you would normally do in this case, but what I've done is to examine corresponding packages in portage, and use the depedencies that they specify, in order to allow them to be built successfully. As far as category is concerned, I have no issue one way or the other.
Is there any reason this ebuild hasn't gone into the portage tree yet? app-admin is almost certainly the proper category since system-configurator is also there, and they are all part of one larger project "si-suite".
Created attachment 45366 [details] A revised systemimager ebuild - further dependencies added I discovered some more missing dependencies that prevented the scripts working as they should; the relevant dependencies have been added. This needs further testing, as I have only been able to do this on my cluster here...
Matthew - haven't got around to looking at this one. Take over if you wish.
Created attachment 60795 [details] ebuild for systemimager-3.4.1 This is an ebuild for the newest version of systemimager (3.4.1 at this time). I modified the existing ebuild and added some patches to get it compiled. Two patches are for the raidtools packages (took them from portage). I don't know if both of them are really necessary, one is for sure. The third patch is for kernel-2.4.25 to get it compiled with gcc-3.4 (took it from http://dl.rocklinux-consulting.de/oss/linux24/gcc340-fixes-v2.4.26-try3.patch) This ebuild is far away from stable but i hope to find some skilled people helping improving it.
Created attachment 60797 [details] ebuild for systemimager-3.4.1 This is an ebuild for the newest version of systemimager (3.4.1 at this time). I modified the existing ebuild and added some patches to get it compiled. Two patches are for the raidtools packages (took them from portage). I don't know if both of them are really necessary, one is for sure. The third patch is for kernel-2.4.25 to get it compiled with gcc-3.4 (took it from http://dl.rocklinux-consulting.de/oss/linux24/gcc340-fixes-v2.4.26-try3.patch) This ebuild is far away from stable but i hope to find some skilled people helping improving it.
Created attachment 60798 [details] ebuild for systemimager-3.4.1 This is an ebuild for the newest version of systemimager (3.4.1 at this time). I modified the existing ebuild and added some patches to get it compiled. Two patches are for the raidtools packages (took them from portage). I don't know if both of them are really necessary, one is for sure. The third patch is for kernel-2.4.25 to get it compiled with gcc-3.4 (took it from http://dl.rocklinux-consulting.de/oss/linux24/gcc340-fixes-v2.4.26-try3.patch) This ebuild is far away from stable but i hope to find some skilled people helping improving it.
Created attachment 60796 [details] ebuild for systemimager-3.4.1 This is an ebuild for the newest version of systemimager (3.4.1 at this time). I modified the existing ebuild and added some patches to get it compiled. Two patches are for the raidtools packages (took them from portage). I don't know if both of them are really necessary, one is for sure. The third patch is for kernel-2.4.25 to get it compiled with gcc-3.4 (took it from http://dl.rocklinux-consulting.de/oss/linux24/gcc340-fixes-v2.4.26-try3.patch) This ebuild is far away from stable but i hope to find some skilled people helping improving it.
Created attachment 60800 [details, diff] Patch for systemimager-3.4.1 raidtools
Created attachment 60801 [details, diff] Patch for systemimager-3.4.1 raidtools (second patch)
Created attachment 60803 [details, diff] Patch for systemimager-3.4.1 kernel-2.4.25 gcc-3.4 fixes
This is one hellish package. Problems with it: 1) It requires a COMPLETE rewrite of its Makefile as the Makefile will wget tarballs from websites and compile them 2) It is not a backup package - more a cluster deployment ("and a bad one at that")
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
