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

[cobalt-users] making a dummy package



Hello,
	I tried quite a few things and found out that you dont actually need a
rpm file in the package so the minimum i got to work was 2 files

packing_list    upgrade_me

so cobalt reads the packing_list first then runs the upgrade script
two files i used below between ----
I run several times with different commands in the upgrade script
------------------ packing_list ------------------
Package: gerald
SCRIPT: upgrade_me
Version: 1.1.1
List File: gerald
REBOOT: no
------------------------------------------

--------------- upgrade_me ------------------------
#!/bin/sh
#chown root /usr/bin/killall

chown admin /etc/inetd.conf
#chown admin /etc/inetd.conf.master
#/usr/bin/killall -HUP inetd >/home/sites/site16/web/bin/marketing/internet/output



exit 0
--------------------------------------------------------

http://www.cobalt.com/support/createpackage.html

some good reading on how to do it I started there and then threw out things to
see what the minumum needed to work was


packing list contains what you have rpm's etc in your package version number
etc and the name of the shell script that does the installation upgrade_me
mines a bit strange coz i was chown some files to admin so my perl script could
overwrite.
basically you just put in upgrade me the commands you wish to run.

its a bit fussy as to how you make the .pkg what i did was make a dir and in
there put 
packing_list and upgrade_me then run

tar -czvf  mypackagename.pkg  *

Dont know if you can tar things on a windows box??? maybe latest winzip can
dont know running linux locally.

then just installed mypackagename.pkg through the web interface it run the
commands then i get the massage something like illegal package format.

you can test it with some commands like

ls /etc > /home/sites/somewhere/testfile

hope this helps
gerald y






On Tue, 24
Jul 2001, you wrote: > Hi Gerald, > 
> So how do I go about making this dummy pkg, does it have to be an executable
> makefile, which guidelines should I use.  Should I just plug the commands
> in, append a pkg extension and try to install it?
> 
> 
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users