Re: [cobalt-developers] Package Un-installation issues on Qube 3

[Michael Stauber <devel@xxxxxxxxxxxxxx>]

Hi Robert,

> Cobalt has a bug in their uninstall script which
> messes up when your package name contains spaces in it. If you notice,
> all of Cobalts packages are named like "Qube3-All-Security-4.0.1-13323"
> with no spaces. This is contradicted in the sausalito manual on page
> 6-13 where the NameTag: variable clearly states that it can be an
> Internationalizable package name string.

Hmm ... very interesting. I'll try to remember that info when it comes to 
naming my packages. Yeah, the manuals are contradicting, in parts obviously 
wrong or omiting a few important details. :o/

"msgunfmt" anyone? <grrr>

> In terms of writing your own stuff, keep at it. It will take reading the
> Sausalito manual about 10 times before it all makes sense.

I finally got my custom pages inserted into the Qube3 interface and learned a 
little more about Sausalito. Mostly by reverse-engineering existing pages or 
trial and error as you suggested. 

In some parts I'm simply cheating on Sausalito as I use one of my PHP scripts 
to read from and to write to a config file directly, fully bypassing the 
handlers. I looked at the handlers and OID stuff, but that seemed more hassle 
than it was worth for simply fetching a few values from a config file and 
rewriting the file from scratch if the admin changes some values through the 
GUI.

So now I've got the XML file with the navigational nodes, have my PHP pages, 
the *.po file, *.schema, *.conf and the handler *.pl - all in the proper 
places where the GUI expects 'em. 

Where I'm currently stuck at is building the RPMs. I know how to build RPMs in 
general and based on /usr/sausalito/devel/templates/spec.tmpl I made a 
specfile for my purposes. However, there is no sample packing_list.tmpl 
anywhere on the Qube (opposed to what the manual says), but ok, I got one 
from an older version of that PKG (same software without GUI) that I can 
modify.

But what's the matter with the makefile in first place and the commands "make 
all, make clean, make install and make rpm"? Somehow they don't seem to fit 
into the scheme and the manuals are kinda elusive on that issue.