Dann, I described the situation a few times, last time when Brian announced to switch away from sisuite.org to systemimager.org. Nobody is actually maintaining the sisuite.org systemconfigurator version, Sean has aknowledged then that he doesn't have time for it and moved forward to other projects. Because we need systemconfigurator for OSCAR and attempts to integrate stuff into the main version failed due to poor response from the official maintainers/developers (this is a few years ago now), I have an own branch which I maintain inside the OSCAR tree. This version is not OSCAR specific, therefore can be used by others, too. The version has moved forward and has received new version numbers.
Brian has proposed that we move the OSCAR systemconfigurator version back into the sisuite.org repository and I can continue to maintain it effectively. I don't care particularly to be official maintainer for this, but I absolutely need to be able to fix issues when they show up in OSCAR and need new releases much more frequently. If there is a maintainer for systemconfigurator (well, didn't see evolution since quite a while) then he should please speak up and say what's going on and how the future of systemconfigurator looks like. I like SC and respect the original development and design. But I can live with a fork, too. Best regards, Erich On Sunday 19 November 2006 20:02, dann frazier wrote: > On Sun, Nov 19, 2006 at 10:52:09AM +0100, Andrea Righi wrote: > > Erich, Dann, > > > > at the moment, if I'm not wrong, systemconfigurator is only maintained by > > Erich in the OSCAR repository: > > > > https://svn.oscar.openclustergroup.org/trac/oscar/browser/trunk/packages/sis/SRPMS > > > > I would like to apply a patch for the YaBoot boot loader (I wrote it > > based on the Erich's version): > > > > --- systemconfigurator-2.2.7/lib/Boot/YaBoot.pm.orig 2006-11-19 > > 10:32:58.000000000 +0100 > > +++ systemconfigurator-2.2.7/lib/Boot/YaBoot.pm 2006-11-19 > > 10:33:01.000000000 +0100 > > @@ -83,6 +83,8 @@ > > $this{bootloader_exe} = > > "$this{root}/boot/yaboot.$this{platform_t}"; > > } elsif (-e $this{root}."/boot/yaboot") { > > $this{bootloader_exe} = "$this{root}/boot/yaboot"; > > + } elsif (-e $this{root}."/usr/lib/yaboot/yaboot") { > > + $this{bootloader_exe} = > > "$this{root}/usr/lib/yaboot/yaboot"; > > } else { > > verbose("Read README file for naming of Yaboot image."); > > carp("Cannot find a Yaboot image.\n"); > > > > Anyway, would it be possible to have a common (official) repository for > > SC? Maybe I could also apply other patches, but I don't know which is > > the last official release... Erich the 2.2.7 is fully based on 2.2.2 or > > there're some piece of code that must be merged? > > > > And what about adding a systemconfigurator repository on > > http://svn.sisuite.org? or do you prefer to have a repository on SF.net > > or OSCAR? > > I can convert the sourceforge cvs repo to svn and host on > svn.sisuite.org if everyone's ok with that. > > But, I don't know where this 2.2.7 release Oscar is based upon came > from. If it is just a local branch of 2.2.2, all of the releases > should be 2.2.2-something - rolling the upstream version is confusing > and breaks upgrade paths (2.2.7-12ef won't upgrade to 2.2.3). ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
