GNOME Bugzilla – Bug 152168
make gnome-mm release
Last modified: 2004-12-22 21:47:04 UTC
with this I mean like one tar bal you have to download containing all the stable bindings. for example: gnome-mm-2.6.0#./configure ; make ; make install will install: # glibmm 2.4 (stable) # gtkmm 2.4 (stable) # libglademm 2.4 (stable) # libgnomecanvasmm 2.6 (stable) # gnome-vfsmm 2.6 (stable) # gconfmm 2.6 (stable) # libgnomemm 2.6 (stable) # libgnomeuimm 2.6 (stable) this is less work for packagers
Are you a packager? What distro are you packaging for?
dropline :)
Do you expect to provide separate binary packages for all of these? If not, then you should. If yes, then can you tell us how this makes life easier for you. There is very little chance of this happening unless you provide a patch (we tried it before, unsuccessfully). After all, the whole point of distro packagers is to do this kind of work. But I'd like to learn about the problems involved.
Please respond.
It just is less work if you just need to download one package and compile and then install it. But I can understand if it is difficult for you guys that it is maybe not worth the effort. I was just wondering why java-gnome has such a collection package and you guys don't.
OK. Not a bug, because a) It's the packagers job to do the difficult stuff so that the user of the package doesn't. b) Having one source tarball and install will encourage packagers to confuse the contents of onen module with another, and to package it differently on different platforms. c) We don't do this for the rest of the GNOME platform. java-gnome is now modular.