[softwaremgmt] MetaPackage schema
Hi Benji, Michael and me looked at the new meta data schema and we had the following observations: We understand that you want to produce one working ymp file for all distros. This does mean that you need to maintain the definition for base repos also in yast, so that YaST does know what base distro is running. So you have a mapping rule in yast-metapackage-handler to map the strings from the ymp file to strings from install.inf or /etc/SUSE-release ? This does mean you will popup an error or warning popup when someone tries to add a repo for a not matching base repo ? Is it still possible to install openSUSE 10.1 repos on SLE-10 for example ? Michael and me think that the "<products>" and "<product>" tags could get a different name, because we associate it with something like "openSUSE 10.2" but not with a single package or pattern. What about "<software>" and "<rpm>" for example ? bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On 25/07/07, Adrian Schröter <adrian@suse.de> wrote:
Hi Benji,
Michael and me looked at the new meta data schema and we had the following observations:
We understand that you want to produce one working ymp file for all distros.
Not necessarily, I think we need the flexibility to be able to have one that will work whatever the distribution. For example on third party media or other situations where the user may not know what distribution they are using. If the user's distribution is already known when using the package search/ software portal then the other distversion information does not have to be included, and so download size is reduced.
This does mean that you need to maintain the definition for base repos also in yast, so that YaST does know what base distro is running. So you have a mapping rule in yast-metapackage-handler to map the strings from the ymp file to strings from install.inf or /etc/SUSE-release ?
There is already a Product.ycp which can be used to query what the base system is. I was going to compare against Product::name which returns "openSUSE 10.2" or "openSUSE 10.3" etc.
This does mean you will popup an error or warning popup when someone tries to add a repo for a not matching base repo ?
That could be done, not certain whether or not it is already provided by the standard package dialogues, I will look into it.
Is it still possible to install openSUSE 10.1 repos on SLE-10 for example ?
It should be, especially if marked as for 10.1 in the YMP.
Michael and me think that the "<products>" and "<product>" tags could get a different name, because we associate it with something like "openSUSE 10.2" but not with a single package or pattern. What about "<software>" and "<rpm>" for example ?
Software sounds good. _ Benjamin Weber -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On Wednesday 25 July 2007 14:44:17 wrote Benji Weber:
On 25/07/07, Adrian Schröter <adrian@suse.de> wrote:
Hi Benji,
Michael and me looked at the new meta data schema and we had the following observations:
We understand that you want to produce one working ymp file for all distros.
Not necessarily, I think we need the flexibility to be able to have one that will work whatever the distribution. For example on third party media or other situations where the user may not know what distribution they are using. If the user's distribution is already known when using the package search/ software portal then the other distversion information does not have to be included, and so download size is reduced.
Yes, we want to design the OBS End-User interface in exact this way atm.
This does mean that you need to maintain the definition for base repos also in yast, so that YaST does know what base distro is running. So you have a mapping rule in yast-metapackage-handler to map the strings from the ymp file to strings from install.inf or /etc/SUSE-release ?
There is already a Product.ycp which can be used to query what the base system is.
I was going to compare against Product::name which returns "openSUSE 10.2" or "openSUSE 10.3" etc.
k, that means that we need to define this string in the OBS as well, so that we can fill in a proper name ... ...
Michael and me think that the "<products>" and "<product>" tags could get a different name, because we associate it with something like "openSUSE 10.2" but not with a single package or pattern. What about "<software>" and "<rpm>" for example ?
Software sounds good.
<software> for <products> and <rpm> for <products> ? -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
On 25/07/07, Adrian Schröter <adrian@suse.de> wrote:
On Wednesday 25 July 2007 14:44:17 wrote Benji Weber:
On 25/07/07, Adrian Schröter <adrian@suse.de> wrote:
Hi Benji,
Michael and me looked at the new meta data schema and we had the following observations:
We understand that you want to produce one working ymp file for all distros.
Not necessarily, I think we need the flexibility to be able to have one that will work whatever the distribution. For example on third party media or other situations where the user may not know what distribution they are using. If the user's distribution is already known when using the package search/ software portal then the other distversion information does not have to be included, and so download size is reduced.
Yes, we want to design the OBS End-User interface in exact this way atm.
This does mean that you need to maintain the definition for base repos also in yast, so that YaST does know what base distro is running. So you have a mapping rule in yast-metapackage-handler to map the strings from the ymp file to strings from install.inf or /etc/SUSE-release ?
There is already a Product.ycp which can be used to query what the base system is.
I was going to compare against Product::name which returns "openSUSE 10.2" or "openSUSE 10.3" etc.
k, that means that we need to define this string in the OBS as well, so that we can fill in a proper name ...
...
Michael and me think that the "<products>" and "<product>" tags could get a different name, because we associate it with something like "openSUSE 10.2" but not with a single package or pattern. What about "<software>" and "<rpm>" for example ?
Software sounds good.
<software> for <products>
and
<rpm> for <products>
I don't think <rpm> is good because a) It could be a pattern. b) It would be rather silly if used on debian system. What do you think about flattening it? i.e. remove the <repositories> and <software> level and do something like: <group> <repository> ... </repository> <repository> ... </repository> <software> ... </software> <software> </software> </group> ? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org
participants (2)
-
Adrian Schröter -
Benji Weber