[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



Hi Robert,

> I can't seem to get a package to un-install. Actually I seem to have
> broken the un-install routine in the Qube 3 because I can't un-install
> any packages now. 

Normally you define if a package as uninstallable in the packing_list of the 
PKG itself. In specific the "Options" line does the trick:

PackageType:           complete
# options:
# uninstallable = you can uninstall the package
# refreshui     = will refresh the admin interface after installing
# refreshcce    = will refresh the backend after installing
Options:               uninstallable,refreshui,refreshcce

So the options "uninstallable,refreshui,refreshcce" will make sure that after 
install the ui and cce are refreshed, but "uninstallable" will make sure that 
the package can be removed from within the GUI.

> I followed the Cobalt Sausalito Developers Guide to
> the letter(that could be the issue). But I still seem to have broke
> something. The un-installer in the Qube UI just hangs at "Initializing
> 0%".

> Anybody have any ideas???? If anyone has a simple mod file for me to
> look at for examples, I would be very appreciative.

I'm also looking for examples for creating additions to the GUI interface. I 
have read DTN14-0-1.pdf and SSDK.pdf multiple times, but as good as that 
documentation might be, it sucks big time when it comes to examples or 
working sample code. The sample PKG Slush-Barn is also a more of a waste of 
time as it lacks the sources, the *.mo locale file and the specfile. 

Could you perhaps help me some pointers or sample code for the GUI stuff?

Just today I spent another six hours tinkering with Sausalito by trying to 
stuff a sample page into the GUI and couldn't get it to work. The entire 
affair really looks like its a no-brainer at first glimpse, but the absolute 
lack of samples and the wide scope of tiny - but important - bits of 
information which the manuals don't cover makes Sausalito a horrible affair.

Sun Cobalt praises Sausalito as open source standard, but I wonder if they 
didn't do things this way with that horrible documentation to keep third 
parties away from messing with the internals. :o(

-- 

Mit freundlichen Grüßen / With best regards

Michael Stauber
mstauber@xxxxxxxxxxxxxx
Unix/Linux Support Engineer