Hello,
Le mardi 3 avril 2007 13:27, Erich Focht a écrit :
> 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).
You have 3 objections:
1/ Moving scripts into RPM or DEB {pre,post}{rm,install} scriptlets
2/ /var/lib/oscar is not the right place for scripts
3/ Renaming scripts
Let me argue a little bit more.
1/ I think it is good to use scriptlets functionnalities provided by RPM and
DEB.
The first reason is that their meaning is whell known by package maintainers.
Second reason is that some opkg scripts have exactly this meaning, so why
don't integrate them into RPM or DEB packages (eg. post_server_rpm_install is
exactly the same meaning as postinstall script of an opkg-server-* package).
For other scripts, which do not fit the RPM or DEB scriptlets, I proposed to
put them in /var/lib/oscar/packages ... huh /opt/oscar/packages, anyway.
You argue that you want to run these scripts manually but this is the work of
opkgc to integrate them in the RPM or DEB packaging. OSCAR package still
contains these scripts separated in the scripts/ dir.
2/ About /var/lib/oscar, I don't mind. Let's put it in /opt/oscar/packages. My
idea behing this was to be a little bit more integrated into distributions
habits. If /var/lib/oscar is far from current OSCAR habits, OSCAR is far from
distributions habits, and it keep OSCAR a bit complex. But, as you say, it
can be done in a second step.
3/ Last point is about scripts name. It is just to be more clear for new
packagers. As I'm writing a script to transform old packaging into new
packaging, this can be done easily. I'm just waiting for other people to see
if they accept this changing.
So, in a few words, for points 2/ and 3/, I don't really mind, I just think we
have to migrate to something more integrated in distribution habits, the
question is: in one step or more.
For point 1/, if {post|pre}{rm|install} scripts of opkg-{server|client|api}-*
packages do nothing, we will have a lot of scripts to launch by a specific
OSCAR mechanism, whereas RPM or DEB mechanisms can just do it out of the box.
Regards,
Jean
>
> 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
--
------------------------------------------------------------------------
Kerrighed inside
http://www.kerrighed.org/
------------------------------------------------------------------------
Jean PARPAILLON - Engineer - PARIS group - Office E210
IRISA-INRIA, Campus de Beaulieu, 35042 Rennes cedex, France
Tél: +33 2 99 84 22 33, Fax: +33 2 99 84 71 71
-------------------------------------------------------------------------
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
