New Comps Groups

[Nicolas Mailhot]

Le mercredi 29 novembre 2006 à 19:19 -0800, Toshio Kuratomi a écrit :

> PS. When we design something new, it should have multicategory support:
> 
> <package>
>   <name>python-gpgme</name>
>   <category>/Language/Python</category>
>   <category>/Security/Cryptography</category>
>   <category>/Development/Library</category>
>   <category>/Internet/CertificateManagement</category>
> </package>

Actually, if I had to redesign the comps model (which probably needs to
be done someday) I'd aim for something like this:

<!-- Official distro classification policy -->

<category name="cid1">
 <!-- All the category metadata, with translations -->
 <title>...</title>
 <summary>...</summary>
 <description>...</description>
</category>

<!-- ... -->

<category name="cidxx">
 <title>...</title>
 <summary>...</summary>
 <description>...</description>
</category>

<!-- Full package list with exhaustive categorisation, individual
packager responsability -->

<content name="all">

<package name="pid1">
 <!-- package in category cid17, cid85 and cid33 -->
 <category ref="cid17"/>
 <category ref="cid85"/>
 <category ref="cid33"/>
</package>

<!-- ... -->

<package name="pidxxx">
 <category ref="666"/>
</package>

</content>

<!-- Predefined repository views, releng domain ? -->

<profile rules="anaconda" use="kdefulldvd">
  <!-- List of groups we want to see in the tool UI -->
  <!-- gid1 is only there to reference the group later -->
  <group name="gid1">
    <!-- Usual title, description, whatever -->
    <title>...</title>
    <description>...</description>
    <!-- All the packages in category cid2, cid33 + package pid7 -->
    <content>
       <category ref="cid2"/>
       <category ref="cid33"/>
       <package ref="pid7"/>
    </content>
  </group>
  <group name="gid2">
    <!-- Group metadata -->
    <content>
      <!-- Only packages in category cid25, cid1 and cid2 -->
      <intersection>
        <category ref="cid25"/>
        <category ref="cid1"/>
        <category ref="cid28"/>
      </intersection>
    <content>
  </group>
  <!-- So far we've only used flat package lists, but anaconda
       wants to have some packages mandatory or default on in groups -->
  <group name="gid3">
    <!-- Group metadata -->
    <content type="mandatory">
      ...
    </content>
    <content type="defaulton">
      ...
    </content>
  </group>
  <!-- ... -->
</profile>

<!-- another anaconda profile -->
<profile rules="anaconda" use="gnomecd">
  <!-- ... -->
</profile>

<!-- A yum profile -->
<profile rules="yum" use="PVR">
  <!-- yum can use groups ... -->
  <group name="gidfoo">
        <!-- Group metadata -->
     <content type="recommended">
        <!-- ... -->
     </content>
     <content type="experimental">
        <!-- ... -->
     </content>
  <group>
  <!-- But is probably happy with the raw categories -->
  <content>
     <!-- ... -->
  </content>
</profile>

<!-- A repoview profile -->
<profile rules="repoview" use="full">
  <content ref="all"/>
</profile>


-- 
Nicolas Mailhot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Ceci est une partie de message num?riquement sign?e
URL: <http://listman.redhat.com/archives/fedora-extras-list/attachments/20061130/aa92061c/attachment.sig>