Mailinglist Archive: zypp-devel (68 mails)
| < Previous | Next > |
[zypp-devel] status (YUMParser)
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Wed, 02 May 2007 10:37:46 +0200
- Message-id: <46384DDA.7050300@xxxxxxx>
Done:
- YUMParser class using RepomdFileReader to get a list of files to parse
and calling corresponding *FileReaders to do the job. YUMParser also
defines callbacks which recieve data from parsers and use CacheStore to
put it into database.
- primary.xml.gz parser almost complete, the rest are just stubs.
Pending:
- patch parser
- suse-primary extensions (are there any docs about these?)
- filelists (both from filelists.xml.gz and primary.xml.gz) [easy]
- other.xml [easy]
- groups
- patterns, products
CacheStore API needed for:
- storing resolvable details (attributes other than NVRAD)
- inserting filelist entries
- changelog entries
My previous estimate was too optimistic :O( I'd say i need five more
days to have all YUMParser jobs done.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
- YUMParser class using RepomdFileReader to get a list of files to parse
and calling corresponding *FileReaders to do the job. YUMParser also
defines callbacks which recieve data from parsers and use CacheStore to
put it into database.
- primary.xml.gz parser almost complete, the rest are just stubs.
Pending:
- patch parser
- suse-primary extensions (are there any docs about these?)
- filelists (both from filelists.xml.gz and primary.xml.gz) [easy]
- other.xml [easy]
- groups
- patterns, products
CacheStore API needed for:
- storing resolvable details (attributes other than NVRAD)
- inserting filelist entries
- changelog entries
My previous estimate was too optimistic :O( I'd say i need five more
days to have all YUMParser jobs done.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |