Hello Jean, I propose to keep things simple in the first steps. We never wanted to completely replace opkg API scripts with the scriptlets provided by RPM or DEB. Also we need the API scripts to be called again, when fixing up the pre or post-configuration.
I don't see us getting rid of the /opt/oscar directory, and there is no reason to do that. That is the traditional place where OSCAR libs and scripts live. Therefore I would very much prefer if you would leave the API scripts also there, in /opt/oscar/packages/*/scripts/ . If you want to invoke those scripts from a scriptlet of RPM or DEB, okay, but that is not really needed, since the scripts are invoked anyway in the installation process/steps. I personally don't like that stuff goes into some /var/lib/oscar/ subdirectory, that's too long to type and find, and too far from the habits we have since 6 years. Besides, /opt/oscar is more visible and natural, because most of the oscar infrastructure goes to /opt, anyway. What we want to solve for now is the dependency issues and get rid of the corresponding part in tha database. Please keep you scripts renaming plan in mind, but let's do that in a second step (if people agree on it at all). Regards, Erich On Tuesday 03 April 2007 11:32, Jean Parpaillon wrote: > Hi all, > I began writing the new opkg API on the devel wiki: > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/BuildOpkg > > - config.xml schema has been commited in subversion few days ago and I had no > comments about it, so I presume it's ok. > - For scripts, I have some questions. > We have now, from a opkg, 3 native (RPM or .deb) packages: api, server and > client. > With RPM and Debian, we can do pre-install, post-install, pre-uninstall and > post-uninstall. > Currently, with opkg, we have these scripts: stup, pre-configure, > post-configure, post-server-rpm-install, post-client-rpm-install, > post-clients, post-install, post-server-rpm-uninstall, > post-client-rpm-uninstall. > I suggest the following linking between current and new packaging: > > Current packaging | New packaging | > Current script | Package | Script | > ============================================================================== > setup | api | pre-install | > pre_configure | api | /var/lib/oscar/packages/ \ | > <package>/pre_configure | > post_configure | api | /var/lib/oscar/packages/ \ | > <package>/post_configure | > post_server_rpm_install | server | post-install | > post_client_rpm_install | client | post-install | > post_clients | api | /var/lib/oscar/packages/ \ | > <package>/post_clients | > post_install | api | /var/lib/oscar/packages/ \ | > <package>/post_install | > post_server_rpm_uninstall | server | post-uninstall | > post_client_rpm_uninstall | client | post-uninstall | > ============================================================================== > > When I say /var/lib/oscar, it's on the server. > > Current packages include a lot of specific scripts in the scripts dir/. I > suggest to put them into /var/lib/oscar/packages/<package>/ > > As many things are changing about packaging, I plan to write a script to > translate old package description to new one, as asked by Steven Blackburn. > In the same time, it can be useful to rename the above files, for better > understanding: > setup -> api-pre-install > pre_configure -> api-pre-configure > post_configure -> api-post-configure > post_clients -> api-post-image > post_install -> api-post-deploy > post_server_rpm_install -> server-post-install > post_server_rpm_uninstall -> server-post-uninstall > post_client_rpm_uninstall -> client-post-install > post_client_rpm_uninstall -> client-post-uninstall > > To implement Erich's idea about kernel dependant packages, the following file > is added: > post-kernel > This script will be put in /var/lib/oscar/kernel-update/<package>-post-kernel > and will be fired by an 'update-kernel-packages' command which is to be > written... > > If everybody agree, I will put all this this stuff in a more developped way > on > the devel wiki. > > Best regards, > Jean > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
