On 21 Jun 2003, seth vidal wrote:
> Hey,
> This is the layout I came up with for the xml template files
>
> <xml 1.0>
<?xml version="1.0"?>
is generated by libxml2. You'll probably want to duplicate its format.
> <yumtemplate>
> <transaction>
> <config>/path/to/yum.conf</config>
> <package action=[update|install|remove]>name/glob</package>
> <group action=[update|install]>name/glob</group>
> </transaction>
> <transaction>
> <config>/path/to/yum.conf</config>
> <package action=[update|install|remove]>name/glob</package>
> <group action=[update|install]>name/glob</group>
> </transaction>
> </yumtemplate>
>
> comments? suggestions? ideas?
Looks lovely. Again, you'll probably want to add quotes:
<package action=["update"|"install"|"remove"]>name/glob</package>
to remain completely consistent with libxml2's output. xmlsysd'd output
is generated by libxml2 if you want to check. Only question I'd have is
whether or not one can put multiple packages or groups in a single
transaction:
<transaction>
<config>/path/to/yum.conf</config>
<package action=[update|install|remove]>name1/glob1</package>
<package action=[update|install|remove]>name2/glob2</package>
<package action=[update|install|remove]>name3/glob3</package>
<group action=[update|install]>name1/glob1</group>
<group action=[update|install]>name2/glob2</group>
...
</transaction>
It would make sense to permit this (so one config file per transaction,
but possibly multiple package/actions per transaction). It's largely a
question of how you want to parse and store the content of the yum/xml
tags -- it isn't a bad idea to make the tags follow the parsing
hierarchy and logic...
rgb
>
> -sv
>
>
> _______________________________________________
> Yum mailing list
> Yum@xxxxxxxxxxxxxxxxxxxx
> https://lists.dulug.duke.edu/mailman/listinfo/yum
>
--
Robert G. Brown http://www.phy.duke.edu/~rgb/
Duke University Dept. of Physics, Box 90305
Durham, N.C. 27708-0305
Phone: 1-919-660-2567 Fax: 919-660-2525 email:rgb@xxxxxxxxxxxx
