[Yum-devel] packagesack/package objects

[Paul Nasrat]

On Mon, 2006-01-30 at 22:11 -0500, seth vidal wrote:
> Hey,
>  This is a layout for something menno and I discussed at lca.

Cool.

> Essentially we'd be getting rid of self.rpmdb and replacing it with a
> rpmdbPackageSack - which is derived from a base packagesack object.

This sounds sane.

> YumBasePackage
>   - YumAvailablePackage
>     - YumAvailableSQLitePackage
>     - YumAvailableXMLPackage
>   - YumLocalPackage
>   - YumInstalledPackage

Are YumInstalledPackage and YumLocalPackage not related (driven by
header so lots of the parsing of prco into YumBasePackage format is the
same).  This ties in to the patch I hacked up in the current
YumInstalledPackage thread to try and unify behaviour.

> YumBasePackageSack
>   - SqliteSack
>   - RpmDBSack
>   - XMLSack
>   - ListSack

These all seem reasonable.
  
> YumBasePackage
>   attributes/properties:
>    - name
>    - arch
>    - epoch
>    - ver
>    - release
>    - requires (as list of tuples)
>    - provides (as list of tuples)
>    - conflicts (as list of tuples)
>    - obsoletes (as lit of tuples)
>    - everything in primary.xml
>    - repo_object
>    - relative url
>    - filelists (as iterator object of some sort)
>    - changelog (as its own object)

That all seems sane.  We probably want to sketch out the methods on
these objects too.  

Paul