[cobalt-users] Re: RaQ 4 PKG "howto"

[Bruce Timberlake <bruce@xxxxxxxxxx>]

> Sun's pkg approach to linux is evil! You will end up with bunch of 
> [stupid] unresolved dependencies and totally incompatable 3-rd party 
> software.

Why is that a PKG specific problem?

> Using RPM packages is the right path, that's Linux after all, time to 
> stop clicking the mouse. 

Well, any sort of package handler is good; RPM has its strong and weak 
points, just like .deb, etc.

> RPM is designed to check versions, architectures, dependencies. Why 
> putting them into stupid tarballs, arm with stupid scripts with 
> --nodeps/--noscripts/--force? 

To make it easier for non-admins to install upgrades without having to know 
how to work a shell, etc.

You don't have to put RPMS in a PKG, you can have it just contain a shell 
script or a tarball of content (maybe web pages or something). Then you can 
roll out the "update" to all your servers automatically via Control 
Station, etc., and be sure that the command will be executed as you want, 
and have a record in the UI that the PKG was installed/run/whatever.  Or 
have a less-skilled admin do the point-click via the UI and manually 
upgrade boxes one at a time.

If you don't like it the PKG mechanism, don't use it.