* Duncan Mac-Vicar P. [Mar 31. 2008 15:09]:

Benji Weber wrote:

...

Greetings All,

Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed. [...]

Well, products is the only open topic with respect of installed and non-installed resolvables. Klaus, Michael, should we agree on something?

It is my understanding that we will follow the same path as with patches: - products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management] Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Duncan Mac-Vicar P. napsal(a):

Klaus Kaempf wrote:

...

It is my understanding that we will follow the same path as with patches:

- products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management]

Yes I am aware of that. Now I am trying to jump from layer 30 to layer 1 and figure out the implementation of the APIs benji pointed out.

This leaves us with one restriction, unless you have a installation url as repo, you won't see any product (which makes sense).

In that case the implementation of installed products would be to look all products (coming from the repo) and give the satisfied ones. is that correct?

I'm afraid this 'might' break (or needn't work correctly) in case of Upgrade from media (Installation->Upgrade) as we often do not have access to network-based repositories when upgrading using CD/DVD media. Lukas

Duncan Mac-Vicar Prett napsal(a):

Lukas Ocilka wrote:

...

I'm afraid this 'might' break (or needn't work correctly) in case of Upgrade from media (Installation->Upgrade) as we often do not have access to network-based repositories when upgrading using CD/DVD media.

The repo is cached locally or?

The repo might but needn't be cached locally (on a target). User downloads DVD of openSUSE 11.0 and boots from it. After that he/she selects Upgrade in the Installation Mode dialog. Then he/she choses the root partition of the system to upgrade and inst-sys initializes the target. If the repository is remote, it might fail as we don't need to have network available. Moreover, on a running system, some products (e.g., Add-Ons) might require a base product to be installed before. If an installation repository of that product is not available (e.g., anymore), solver will keep requesting it or might offer not to install the Add-On - even if the base product is installed and all dependencies (but missing product) are fulfilled. L.

Dne Monday 31 of March 2008 15:41:42 Klaus Kaempf napsal(a):

* Duncan Mac-Vicar P. [Mar 31. 2008 15:09]:

...

Benji Weber wrote:

...

Greetings All,

Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.

[...]

...

Well, products is the only open topic with respect of installed and non-installed resolvables. Klaus, Michael, should we agree on something?

It is my understanding that we will follow the same path as with patches:

- products are not 'installed'. [their 'is_installed?' state is computed at runtime] - products are solvables and come in a .solv file - each product will have a distinct package (i.e. suse-release for the distribution) which lists mandatory packages (as dependencies). [this is required to enable 'rpm-only' software management]

Since we have to work also without any repository (and thus without any product to be computed), we will need to adapt this part of YaST functionality to get the product information from the related package. 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

On 01/04/2008, Michael Andres wrote:

On Mon, Mar 31, Benji Weber wrote:

...

Currently in factory Product::name, Product::distversion etc all return an empty string. Probably because there is no product installed.

Is it planned to have products installed once zypp supports them again, or will Product.ycp obtain its data from somewhere else? Or is

Product (Pattern,Patch) will no longer be installed. Instead of this it is computed whether a Products dependencies are satisfied. If so, it should be treated as formerly an installed Product.

2 of the main differences to 'installing a Product':

- If one disables or removes the repository providing the product, the product is gone.

- If the product you installed gets 'damaged' (it's requirements are not fullfilled), it is gone.

Is it likely to be implemented before beta1? It would be nice if people could test YMP things such as installing codecs and using packman's YMPs earlier on in beta phase. Especially as I have exams all through the final release cycle so won't be doing bugfixing. Also Product::name alone is used in at least 12 different ycp files, so I suspect lack of product is going to break other things. -- Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org