Mailinglist Archive: zypp-devel (230 mails)
| < Previous | Next > |
Re: [zypp-devel] collect pending AIs thread
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Wed, 27 Feb 2008 18:08:46 +0100
- Message-id: <47C5991E.8020409@xxxxxxx>
Stefan Schubert wrote:
Hmm, an interesting thread also for zypper {info,lu,up,se,...} -t
{pattern, product} (i guess it applies also to product(?)) :O) This very
much changes the way how lu and up works (e.g. zypper lu -t pattern
doesn't work now).
Let's provide the functionality through a libzypp API:
- determine whether a pattern/product is installed
- get pattern/product 'contents' (already listed in the app layer
requirements)
- determine whether there is an update available for pattern (solver
algorithm)
But we won't be able to tell whether a pattern/product is installed
without repositories (target only) anymore. Is that OK?
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
- Currently there is no functionality when a pattern will be "deleted".
Is this still an valid user input in the UI due the fact that we do not
install
patterns anymore ?
Hmm, an interesting thread also for zypper {info,lu,up,se,...} -t
{pattern, product} (i guess it applies also to product(?)) :O) This very
much changes the way how lu and up works (e.g. zypper lu -t pattern
doesn't work now).
Let's provide the functionality through a libzypp API:
- determine whether a pattern/product is installed
- get pattern/product 'contents' (already listed in the app layer
requirements)
- determine whether there is an update available for pattern (solver
algorithm)
But we won't be able to tell whether a pattern/product is installed
without repositories (target only) anymore. Is that OK?
jano
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |