Dne pondělí 02 červenec 2007 14:58 Michael Andres napsal(a):

On Sun, Jul 01, Duncan Mac-Vicar P. wrote:

...

Hi

We have to think about the sequence and layers of configuration to make it consistent this time.

I list the requirements that come to my mind

- the most important cfg option is the root where you are operating on. In former times this was a Target option, and I think it still is (????)

- known repositories raw metadata path, binary cache path, system architecture, etc, needs to be easily configurable/overridable. A zypp.conf file (ini file) would be a nice way to do it.

So we have to determine the workflow:

- when to set the target root - when do we read values from the config file

Let's create a class that grants access to all these config values. An Instance of this class is passed to ZYpp upon construction.

ZYpp and it's subcomponents have to be adapted to take all config values from this context class, and use them to initialize their's subcomponents.

That way e.g. ZYpp::targetInit would loose it's 'root' argument. Zypp will use the argument provided by the context class instead. That's probabely the most significant change, because zypper/pkg-bindings have to tell the root path quite early in their workflow (before accessing ZYpp).

This cannot work for the installation, since you cannot access the root before the target system gets formatted and mounted and you need to use ZYPP for software selection. We need a way to change the target path while ZYPP is running. It is essential for the installation and we need it ASAP to start testing the installation. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz

Dne úterý 03 červenec 2007 14:15 Klaus Kaempf napsal(a):

* Jiri Srain [Jul 03. 2007 14:11]:

...

This cannot work for the installation, since you cannot access the root before the target system gets formatted and mounted and you need to use ZYPP for software selection.

We need a way to change the target path while ZYPP is running. It is essential for the installation and we need it ASAP to start testing the installation.

Do we need to change the target path ?

If there should be valid what Michael wrote: --- snip --- That way e.g. ZYpp::targetInit would loose it's 'root' argument. Zypp will use the argument provided by the context class instead. That's probabely the most significant change, because zypper/pkg-bindings have to tell the root path quite early in their workflow (before accessing ZYpp). --- snap --- then we do (before accessing ZYpp).

Wouldn't it be sufficient to delay the start of the target until after the root partition is formatted and mounted ?

Software selection should be possible without initialized target.

Yes, if target can be initialized later, then it can work. Installation into directory will probably need some update as well (currently it initializes target and later moves it, but I don't see any reason why it could not work the same way as during normal installation). Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz

Dne úterý 03 červenec 2007 14:40 Michael Andres napsal(a):

On Tue, Jul 03, Jiri Srain wrote:

...

Dne pond??l?? 02 ??ervenec 2007 14:58 Michael Andres napsal(a):

...

On Sun, Jul 01, Duncan Mac-Vicar P. wrote:

...

Hi

We have to think about the sequence and layers of configuration to make it consistent this time.

I list the requirements that come to my mind

- the most important cfg option is the root where you are operating on. In former times this was a Target option, and I think it still is (????)

- known repositories raw metadata path, binary cache path, system architecture, etc, needs to be easily configurable/overridable. A zypp.conf file (ini file) would be a nice way to do it.

So we have to determine the workflow:

- when to set the target root - when do we read values from the config file

Let's create a class that grants access to all these config values. An Instance of this class is passed to ZYpp upon construction.

ZYpp and it's subcomponents have to be adapted to take all config values from this context class, and use them to initialize their's subcomponents.

That way e.g. ZYpp::targetInit would loose it's 'root' argument. Zypp will use the argument provided by the context class instead. That's probabely the most significant change, because zypper/pkg-bindings have to tell the root path quite early in their workflow (before accessing ZYpp).

This cannot work for the installation, since you cannot access the root before the target system gets formatted and mounted and you need to use ZYPP for software selection.

I don't want to access the target before targetInit. The idea was just to announce the 'root' you are going to use later.

This should work for standard installatoin, but not for instlalation into the directory, since the directory is specified in the same proposal as software. There we need to specify the root after ZYPP is already been used for other purposes. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz