Mailinglist Archive: yast-devel (177 mails)
| < Previous | Next > |
Re: [yast-devel] Direction of YaST Architecture?
- From: Thomas Goettlicher <thomas.goettlicher@xxxxxxx>
- Date: Fri, 11 Feb 2011 16:05:27 +0100
- Message-id: <201102111605.28226.thomas.goettlicher@suse.de>
On Friday, February 11, 2011 03:43:11 pm Robert Schweikert wrote:
"Configuration module layer" or what ever.
--
Thomas Goettlicher
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
Hi,I agree lib isn't a prefect name for it. Feel free to propose a better name.
On 02/11/2011 05:24 AM, J. Daniel Schmidt wrote:
On Thursday 10 February 2011 23:21:17 Robert Schweikert wrote:
Attached is a revision of my original diagram incorporating some of the
design style of the ASCII art above.
Differences:
- There is no lib common, the lib common layer of the ASCII art diagram
is implemented by a modularized layer called "Configuration Modules".
You only gave it another name.
I never said that the thing Thomas an I called "common lib" should be one
blob, that any module has to load even if does not need it.
Correct, but using "lib" as a name implies that this is one piece. A
library on the system is in one piece, you cannot load half of libc.
"Configuration module layer" or what ever.
<snip>
Reading your comments I really think that we basically meant the same,
Yes, I think we are pretty much on the same page. That's why I attempted
to somewhat merge the two presentations of the architecture diagram.
And it appears that I have succeeded.
Robert
--
Thomas Goettlicher
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
| < Previous | Next > |