Re: [PATCH 1/2] opensuse: Recognize future versions

[Fabiano Fidêncio <fabiano@xxxxxxxxxxxx>]

On Sun, Aug 10, 2014 at 7:01 PM, Lasse Schuirmann <lasse.schuirmann@xxxxxxxxx> wrote:

2014-08-10 18:24 GMT+02:00 Fabiano Fidêncio <fabiano@xxxxxxxxxxxx>:

> On Sun, Aug 10, 2014 at 4:55 PM, Lasse Schuirmann
> <lasse.schuirmann@xxxxxxxxx> wrote:
>>
>> ---
>>  data/oses/opensuse.xml.in | 50
>> +++++++++++++++++++++++++++++++++++++++++++++++
>>  1 file changed, 50 insertions(+)
>>
>> diff --git a/data/oses/opensuse.xml.in b/data/oses/opensuse.xml.in
>> index c368d10..d424b5c 100644
>> --- a/data/oses/opensuse.xml.in
>> +++ b/data/oses/opensuse.xml.in
>> @@ -418,4 +418,54 @@
>>      </resources>
>>    </os>
>>
>> +  <!-- Generic entry for future openSUSE releases. Please update the
>> +       'upgrades', 'derives-from', 'volume-id' and 'resources' nodes
>> +       accordingly each time you add a new (specific) entry for a new
>> +       release. -->
>> +  <os id="http://opensuse.org/opensuse/unknown">
>> +    <short-id>opensuse-unknown</short-id>
>> +    <_name>openSUSE</_name>
>> +    <version>unknown</version>
>> +    <_vendor>openSUSE</_vendor>
>> +    <family>linux</family>
>> +    <distro>opensuse</distro>
>> +    <upgrades id="http://opensuse.org/opensuse/13.1" />
>> +    <derives-from id="http://opensuse.org/opensuse/13.1" />
>> +    <release-status>prerelease</release-status>
>> +
>> +    <media arch="i686">
>> +      <iso>
>> +        <volume-id>openSUSE-1([4-9]..|3.[2-9])-DVD</volume-id>
>> +        <system-id>LINUX</system-id>
>> +        <publisher-id>SUSE LINUX GmbH</publisher-id>
>> +      </iso>
>> +      <kernel>boot/i386/loader/linux</kernel>
>> +      <initrd>boot/i386/loader/initrd</initrd>
>> +    </media>
>> +    <media arch="x86_64">
>> +      <iso>
>> +        <volume-id>openSUSE-1([4-9]..|3.[2-9])-DVD-x86_64</volume-id>
>> +        <system-id>LINUX</system-id>
>> +        <publisher-id>SUSE LINUX GmbH</publisher-id>
>> +      </iso>
>> +      <kernel>boot/x86_64/loader/linux</kernel>
>> +      <initrd>boot/x86_64/loader/initrd</initrd>
>> +    </media>
>> +
>> +    <resources arch="all">
>> +    <!-- http://en.opensuse.org/Hardware_requirements -->
>> +      <minimum>
>> +        <cpu>500000000</cpu>
>> +        <n-cpus>1</n-cpus>
>> +        <ram>1073741824</ram>
>> +        <storage>3221225472</storage>
>> +      </minimum>
>> +      <recommended>
>> +        <cpu>2400000000</cpu>
>> +        <ram>2147483648</ram>
>> +        <storage>5368709120</storage>
>> +      </recommended>
>> +    </resources>
>> +  </os>
>> +
>>  </libosinfo>
>> --
>> 1.9.3
>>
>> _______________________________________________
>> Libosinfo mailing list
>> Libosinfo@xxxxxxxxxx
>> https://www.redhat.com/mailman/listinfo/libosinfo
>
>
> I didn't get the idea of this patch.
> Just create a generic entry for future releases? is it really valid? Or do
> you need it for something else?
>
> Best Regards,
> --
> Fabiano Fidêncio

I personally dont need it for something specific.

1. We have such a thing for Fedora. In general it would be nice to
recognize future images, also given that distributions might not ship
the most recent version of libosinfo.
2. In case of openSUSE I'm confident that we can link the openSUSE
express installation script (patches will come in the next week or so)
to this generic future entry so people will be able to express install
a recent openSUSE ISO even if they use a libosinfo package from two
years ago. (I think thats the case with debian.)

I spoke with Richard Brown (in CC) from openSUSE who helped me
creating a JEOS installation script for openSUSE and he stated that
this would ease his work a bit, especially having the entry for the
factory images. Its not much work so I've done it.

Lasse

Makes sense.

Thanks for the explanation.

Best Regards,

--

Fabiano Fidêncio

_______________________________________________
Libosinfo mailing list
Libosinfo@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libosinfo