Hi! Please find attached perceus-1.3.1.ebuild. Perceus is the next generation of enterprise and cluster provisioning toolkit. Created by the developers of Warewulf (one of the most utilized Linux cluster toolkits), Perceus redefines the limits of scalability, flexibility and simplicity. Perceus has the advantage of being planned out from inception, and with this we are able to deliver what we feel is the definitive solution for all cluster platforms regardless of their clustering needs or software budget. I suggest sys-cluster/perceus for its home. This packages depends on a Cpan ebuild which i have attached because I couldn't get it inside of the perceus ebuild. Your time in getting this ebuild into the Gentoo tree is much appreciated by all. Thank you and keep up the good work!
Created attachment 133101 [details] perceus-1.3.1.ebuild
Created attachment 133102 [details] Net-ARP-1.0.1.ebuild Cpan Dependency for Perceus I know its not advised to add Cpan ebuilds, but Perceus requires this Perl module.
Comment on attachment 133102 [details] Net-ARP-1.0.1.ebuild Cpan Dependency for Perceus This should go into dev-perl/Net-ARP
Hi. I've seen probably an earlier version of your ebuild somewhere on rafb.net (it was in teh Google cache) wher you installed perceus.rc and perceus.conf files (to /etc/init.d and /etc/conf.d). Those files are probably still needed, why did you remove that phase from your ebuild? Could you please add the files and the install code there? I'd really appreciate that, thanks!
(In reply to comment #4) > Hi. I've seen probably an earlier version of your ebuild somewhere on rafb.net > (it was in teh Google cache) wher you installed perceus.rc and perceus.conf > files (to /etc/init.d and /etc/conf.d). Those files are probably still needed, > why did you remove that phase from your ebuild? Could you please add the files > and the install code there? I'd really appreciate that, thanks! > Those files you refer to, are non-existent and never were a part of the original perceus build. What happened was this is my first ebuild. So I used another ebuild as a template. I forgot that hard coded into my ebuild. I realized this error while attempting to build it with the perceus devs. They asked me why it was looking for files that were never part of their package. I realized then that I made an error ,and removed those lines. So no those will not be re-added to the ebuild because they were never really a part of it. I thank you in your interest in this ebuild and hope it leads to its eventual adoption into the Gentoo Portage Tree.
OK. Thank you for reply. It tested my perceus build now and the init script seems to be almost correct, I had to edit it a bit, but I will verify if this was necessary, because it could have been just my screwed system :D. Once more, thank you for this ebuild.
(In reply to comment #6) > OK. Thank you for reply. It tested my perceus build now and the init script > seems to be almost correct, I had to edit it a bit, but I will verify if this > was necessary, because it could have been just my screwed system :D. Once more, > thank you for this ebuild. > First of all I'm not sure what you are doing. This program requires no Init script. It runs from the command line , as a process. You need to view the Perceus documentation at http://www.perceus.org/portal/documentation .
I know what I'm doing and I've read the documentation. The init script is good to assure that some of the support services were started/to start them. It is created in /etc/init.d/perceus and does what I want it to do.
(In reply to comment #8) > I know what I'm doing and I've read the documentation. The init script is good > to assure that some of the support services were started/to start them. It is > created in /etc/init.d/perceus and does what I want it to do. > I see now what you are trying to do. And I also see that this feature has failed some where between version 1.3.0 and 1.3.1. I will look into it tonight , an will post an update or patch to resolve this issue. If you know the problem please make a suggestion as they are always welcome.
(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. Heuristics show that no Gentoo developer has commented on your ebuild. 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
