https://bugzilla.novell.com/show_bug.cgi?id=481502 User er258@cam.ac.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=481502#c9 --- Comment #9 from Edward Rosten <er258@cam.ac.uk> 2009-03-03 16:01:17 MST ---
This is because you are doing it wrong, since some time we are providing you tools to do just that in automated way, if your software is opensource, you can use the opensuse buildservice to fully automate this task and just add a repository to your machines and install updated software from there.. now if your software is propietary, you can run a private obs-server instance, it is opensource, we can also assist you in setting it up in the opensuse-buildservice mailing list.
The buildserver looks to be a good solution for quite a lot of tasks, but I doubt I can get it installed on all the clusters I use. Also, as far as I can tell, it builds whole packages, which will require root prelidges to install. Most people whi I know who use clusters use quite rapidly changing hand-hacked code, so I'm not sure it's the right tool in this case.
Doing this also provides other side-effect advantages like much reduced packages size, bandwidth saving, less IO in the buildservers.. reduced compilation time as when static libraries are there libtool has to create separate objects for PIC and non-PIC code...there are probably many other advantages that Im missing here too ;)
I can see that. I also take the point that producing -static RPMs is much more work. I had a go, and it required considerably more work than removing the .a, though it is fairly mindless work. Will you accept patches to spec files? I suspect that if the process is user driven then a quite small set of libraries will end up with static versions: only those for which it is useful. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.