On Thursday 22 March 2007 14:34, Jean Parpaillon wrote: > I've commited a draft of a new config.xml schema. > I tried not to break everything but some things needs changing, in its actual > form, most packages won't build with the new schema. Of course, this is a > draft so it can evolve. > In the commit is included a sample config.xml as everybody don't speak xsd > fluently :-) > > Erich pointed out a functionnality which must be implemented on packages > which > concerns kernel related packages. > The issue is: kernel related packages (drivers, for instance) needs some work > (typically, recompilation) when a new kernel is installed. This could be done > automatically. > My idea is:
Jean, I have a problem with your wording. You are describing exactly what I described in the oscar-core phone meeting two days before and call it your idea. This is unacceptable for me personally and is a BAD THING to do in an open source project. I was pushing this since more than one year whenever a kernel dependent package appeared at the horizon. Only those days there was dissense in the way to implement it. Now the rework of config.xml due to the opkg compiler is an opportunity to attack the problem again. By the way, opkgc is another candidate for this kind of issues. To make it clear: the opkg compiler (opkgc) is an idea developed by Brian Finley and myself at the OSCAR conference in St. John's (2006). The design was presented by myself at the ORNL OSCAR meeting in January 2007. Luckilly Geoffroy had xslt/python code he could reuse from his virtualization work which does similar morphings of files as we need, so we have now an implementation of the opkc idea based on that code. > such a package contains a 'post-kernel' file which is an executable, beside > post-install, pre-install and other scripts. This exec do the work needed > when kernel is updated on the client. > There is a command 'update-kernel-modules' which can be launched each time a > kernel is updated. This command launch each registered 'post-kernel' file. > This command can not be launched automatically, because we can not re-package > each kernel packages for every distributions. > Nevertheless, on some distros, this mechanism already exists so the opkg > compiler could make the 'post-kernel' script to be registered to the right > tool (the existing update-kernel-module on the distro). > > Am I clear ? Does this makes sense ? For me it makes sense, of course. After all it was my idea. I was expecting from you to describe how you mark in a config.xml file the kernel dependency. Sure, we can look it up in the schema, but it is more practical to give a tiny example, that reaches more people. > > Best regards, > Jean Best regards, Erich ------------------------------------------------------------------------- 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 Oscar-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-devel
