Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
Re: [zypp-devel] Extending pattern definition
- From: Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx>
- Date: Fri, 22 Jun 2007 15:45:50 +0200
- Message-id: <200706221545.51656.dmacvicar@xxxxxxx>
On Friday 22 June 2007 15:23:11 Jiri Srain wrote:
> The workflow must be defined the way that it will properly run which wizard
> is needed. It can check which dialogs to run depending on packages which
> are installed. In your case, if the pattern contains both sendmail and
> postfix, it should ask user in the first step. Obviously if we ship
> sendmail and postfix, user selects this pattern but installs eg. qmail, the
> pattern workflow cannot take care of it.
That exactly my point. How are you going to know which packages a
pattern "contains"?. Only the solver knows.
You would need to do a 2nd stage kind of solving (looking for package names
matching) after the solver runs (and you can still not be sure which pattern
is the guilty one that selected the package. ), So you are putting more and
more logic in the UI and breaking all the improvements from the old
selections to patterns.
So as usual we are abusing the solver, the language and the UI/Controller,
because at the end a workflow has _nothing_ to do with the pattern itself but
with the pattern installation result (specially individual software)
The correct way to do this would be using dependencies, so if a certain
package gets installed, a worflow or special trigger file (part of the module
package) is also grabed and installed. The installation detects this and
starts the workflow. This only works if the workflow is run after the
software is installed, but I guess you can't configure the software if it is
not installed.
--
Duncan Mac-Vicar Prett
Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> The workflow must be defined the way that it will properly run which wizard
> is needed. It can check which dialogs to run depending on packages which
> are installed. In your case, if the pattern contains both sendmail and
> postfix, it should ask user in the first step. Obviously if we ship
> sendmail and postfix, user selects this pattern but installs eg. qmail, the
> pattern workflow cannot take care of it.
That exactly my point. How are you going to know which packages a
pattern "contains"?. Only the solver knows.
You would need to do a 2nd stage kind of solving (looking for package names
matching) after the solver runs (and you can still not be sure which pattern
is the guilty one that selected the package. ), So you are putting more and
more logic in the UI and breaking all the improvements from the old
selections to patterns.
So as usual we are abusing the solver, the language and the UI/Controller,
because at the end a workflow has _nothing_ to do with the pattern itself but
with the pattern installation result (specially individual software)
The correct way to do this would be using dependencies, so if a certain
package gets installed, a worflow or special trigger file (part of the module
package) is also grabed and installed. The installation detects this and
starts the workflow. This only works if the workflow is run after the
software is installed, but I guess you can't configure the software if it is
not installed.
--
Duncan Mac-Vicar Prett
Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |