Mailinglist Archive: zypp-devel (115 mails)
| < Previous | Next > |
Re: [zypp-devel] Important open issues inside zypp - providing files
- From: Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>
- Date: Wed, 4 Jul 2007 10:08:55 +0200
- Message-id: <200707041008.55793.dmacvicar@xxxxxxx>
On Tuesday 03 July 2007 15:46:45 Jan Kupec wrote:
> 2) There is a special request to have replacement for
> zypp::Source::provideDirTree(Pathname dir_r, media_nr);
> which is used e.g. by product creator.
>
> This could be solved on Fetcher level by adding
> Fetcher::enqueDir(OnMediaLocation dir, bool recursively);
What does the product creator use provideDirTree for?
provideDirTree in high level APIs is evil, as it means you are downloading a
bunch of files, you don't know how, their checksums, etc. So I would prefer
keeping provideDirTree where it is (Media) or at most, wrap it into
MediaSetAccess, but not in Fetcher.
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> 2) There is a special request to have replacement for
> zypp::Source::provideDirTree(Pathname dir_r, media_nr);
> which is used e.g. by product creator.
>
> This could be solved on Fetcher level by adding
> Fetcher::enqueDir(OnMediaLocation dir, bool recursively);
What does the product creator use provideDirTree for?
provideDirTree in high level APIs is evil, as it means you are downloading a
bunch of files, you don't know how, their checksums, etc. So I would prefer
keeping provideDirTree where it is (Media) or at most, wrap it into
MediaSetAccess, but not in Fetcher.
Duncan
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |