Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by grandalf on Thursday August 30, 2012 @02:08AM
(#4453259)
Does RPM have any advantages?
Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by Spidler on Thursday August 30, 2012 @02:38AM
(#4453330)
Better integrity checks, mostly. Built in checksums of files, stricter limits on what you can do as a package ( no controlling terminal and so on ) whereas in deb it's "optional" and "flexible" (aka. not built in and maybe people will get together and decide something)
rpm has some build time analysing tools to track library (.so, python, perl, php, ruby imports) use and annotate this as dependencies.
This above feature is one that causes the mess when you don't have the full dependency graph for a package, because rpm by itself does no dependency resolution.
Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by noselasd on Thursday August 30, 2012 @02:48AM
(#4453351)
As a developer, I'm actually able to easily package stuff with rpm. creating .debs is stupidly frustrating
Re:The truth about Goobuntu: Google's in-house desktop Ubunt...
by vidarh on Thursday August 30, 2012 @05:00AM
(#4453713)
Whenever I've wanted to package .deb's I've just blatantly ignored the official way, and opted for a much simplified setup (write the control file and the pre/post-int scripts, and use a Makefile to build the filesystem hierarchy required and run the appropriate tools).
I agree, though, as much as the RPM spec files are horrible, it's still overall simpler.
A good StackExchange thread: http://unix.stackexchange.com/questions/634/what-are-the-pro...