On Jan 20, 2012, at 4:04 PM, Henrik Ingo wrote: > On Tue, Jan 10, 2012 at 10:15 AM, Henrik Ingo <henrik.i...@avoinelama.fi> > wrote: >> Perhaps just give me most recent version of Fedora for starters, that >> should work best. > > Scratch that. Fedora 16 is completely broken with traditional init > scripts. (And I don't have much nice to say about systemd native > scripts either...) I wonder if this is even LSB complaint? Anyway, > Drizzle rpms won't work on Fedora 16 for the time being. So we need to > setup RHEL/Centos 6 machines to build our rpms. (kind of need to do it > anyway) >
Forgive my stupidity but… are the INIT scripts even required for the Jenkins builds? I think doing some kind of 'install/start/restart/etc' stuff would be nice… but ideally, the primary need for the RPM build in Jenkins is to ensure that any updates to the drizzle source don't break RPM builds…. and within the RPM build the test suite is run… so tests are covered at least. As for SysVINIT -> SystemD I can help with this… I'll try and work on this soon. This might be where we need to split packaging for Fedora/RHEL …. though we might be able to make the builds conditional to support SysVInit and SystemD depending on what the build target is. --- derks _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
