Mailinglist Archive: yast-devel (177 mails)
| < Previous | Next > |
Re: [yast-devel] Direction of YaST Architecture?
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Thu, 10 Feb 2011 15:29:47 +0100
- Message-id: <20110210142946.GD1265@heron.suse.de>
* Thomas Goettlicher <thomas.goettlicher@xxxxxxx> [Feb 10. 2011 15:22]:
Not quite.
Yes.
And what is 'lib shell' ?
A CLI interface should also sit on top of 'yast modules'.
The 'common lib' is too low level. I would expect it to be like Augeas
for config file editing. Whats the value of such an API over 'vi' ?
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
Your attached diagram looks similar to the overview designed by jdsn and me:
Not quite.
+---+---+---+---+ +--------------+
| Q | N | g | c | |webyast client|
| t | C | t | m | +------+-------+
| | | k | d | |
+---+---+---+ | http
| libyui | | |
+-----------+ +-----------+---+ +------+-------+
| lib shell | | yast modules | | rest service |
+-----------+--------+---------------+----------+--------------+
| common lib: reads/writes config files, starts/stops services |
| integration of polkit and zypp |
+--------------------------------------------------------------+
| SYSTEM |
+--------------------------------------------------------------+
Perhaps rest service should sit on top of yast modules.
Yes.
And what is 'lib shell' ?
A CLI interface should also sit on top of 'yast modules'.
The 'common lib' is too low level. I would expect it to be like Augeas
for config file editing. Whats the value of such an API over 'vi' ?
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
| < Previous | Next > |