Le jeudi 22 mars 2007 19:28, Steven Blackburn a écrit :
> If the new config files contain the same sort of data, would it be possible
> / efficient use of time to write an xslt file to convert old files to the
> new format?
Yes, that make sense.
Anyway, I have to write 2 xslt: either 1 for old and 1 for new schemas, either
1 for new schema and 1 for conversion...
>
> Appologies if this is a silly idea / would take too much time. I haven't
> been following the changes but might help adoption of the new format if it
> is easy to convert.
>
> Steve.
Jean
>
> Jean Parpaillon <[EMAIL PROTECTED]> wrote:
> Just for information:
> Do I need to spend time writing templates for old schema ?
> If people agree to rewrite their config.xml to the new form, I'm will
> develop opkgc regarding this new schema, but if people need to use opkgc
> and don't have time to update their config.xml, I can debug current
> templates regarding current schema.
>
> Regards,
> Jean
>
> Le jeudi 22 mars 2007 14:34, Jean Parpaillon a écrit :
> > Hi all,
> > 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:
> > 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 ?
> >
> > Best regards,
> > Jean
--
------------------------------------------------------------------------
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
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel
