On Tuesday 05 June 2007 03:41, Jean Parpaillon wrote: > Hi, > Sorry for answering late but I was looking after my wife's health since > wednesday.
Hi Jean, Sorry to hear that, i hope she will feel better very soon. > > Le Wednesday 30 May 2007 21:01:32 Geoffroy Vallée, vous avez écrit : > > Hi all, > > > > Since we have to use OPKGC as soon as possible, OPD has to be reviewed to > > fit our new needs. I quickly wrote a short description of these > > requirements: > > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/DevOPD2 > > I have some questions/remarks. > 1/ The OPD repository description looks like an opkg description. Is it the > case ? Why is there informations about license, maintainer and so on ? I do not know... i took the basic stuff from the previous OPD schema and just updated it. My goal is not currently to break too many things, i just try to have something that works. :-) > > 2/ About config.xml, what are the informations in the config.xml you need > for opd and which are not in the opkg-<name> package description (obtained > by "apt-cache show " or "yum info" ? > If you really need some infos more from config.xml, I suggest to include > them, formatted, in the package description, ie: > Description: > This is a nice package blah blah blah. > OSCAR::Field1: Value > OSCAR::Field2: Value > > If this solution fits you, please let me know which part of the config.xml > file you need so that I can update opkgc. I do not think this is a suitable solution for what we want to do. I think that many parts of OSCAR (for instance ODA for what i know) are using the config.xml file. Not having these files will therefore imply deep modification of the code, something that at least right now i cannot afford. However, i may be wrong. But in that case, someone else will have to update the code (as i said i do not have the time for that right now). To summarize, i try to not break other OSCAR components (e.g. selector, ODA). Also note that the current OPD code is using the oscar_packages.xml file, not the config.xml file. But they are pretty similar (package description is not handle in the same way for OPKG directly included into OSCAR and those available via OPD). It is not mandatory to include the config.xml file for OPKG available via OPD but we will have to deal with that for OPKG directly included into OSCAR. > > Regarding your solutions: > 1 - putting the config.xml on the repository requires to write specific > code to handle its upload/download/management. We just need the code to download these files. The current code already uses config.xml files so no need to modify it. > 2 - using config.xml from inside a package requires to extract (part of) > the package to get information about it, before using it. I guess we can create a separate package and just have to install it (no dependences with other packages). But then we "install" something even if we do not want to use the package, it pollutes the system. On the other hand, it is then easy to know about packages update. I do not have a strong feeling about these points (except that we need an easy way to know the package status on the compute nodes), i just want to be sure that i will implement something that fits our needs. Note that the basic code is already in trunk. > > > Note that i plan to implement a separate tool (named OPD2) in order to > > not break the current OPD and therefore be able to use the old OPKG API > > until we are able to fully switch to the new API. > > > > Please let me know ASAP if you have remarks/comments, i would like to > > implement OPD2 within the next few days. > > > > Thanks, > > Regards, > Jean -- Geoff ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
