On Wed, Aug 13, 2014 at 5:16 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..e6d5120 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-([2-9][0-9]\.[0-9]+|1([4-9]\.[0-9]+|3\.([2-9][0-9]*|1[0-9]+)))-DVD</volume-id> Seems we ended up with much more complex expression than we'd want to use. Looking at the Fedora's future version regex and keeping in mind that patterns aren't so different between suse and fedora versions, I'm pretty sure you can come up with something much simpler if you simply take fedora's regex and modify it to suit suse. --- Zeeshan Ali (Khattak) ________________________________________ Befriend GNOME: http://www.gnome.org/friends/ _______________________________________________ Libosinfo mailing list Libosinfo@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libosinfo
