[Users] 3.1 packages now mostly noarch?

26 Jul 2012

      --_db293c12-8a38-4a40-a418-2777b79f5e1e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I just noticed something different about=20
http://www.ovirt.org/releases/3.0/rpm/Fedora/16/ vs=20
http://www.ovirt.org/releases/3.1/rpm/Fedora/17/ and certain packages.

Previously in 3.0=2C packages like ovirt-engine* only ran on 64-bit=20
systems (x86_64)=2C while other packages were noarch. Now it seems most of
 the packages are noarch. Was this intentional? It's a nice surprise=20
anyway if it is.

- Nick 		 	   		  =

--_db293c12-8a38-4a40-a418-2777b79f5e1e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>
I just noticed something different about=20
http://www.ovirt.org/releases/3.0/rpm/Fedora/16/ vs=20
http://www.ovirt.org/releases/3.1/rpm/Fedora/17/ and certain packages.<br>
<br>
Previously in 3.0=2C packages like ovirt-engine* only ran on 64-bit=20
systems (x86_64)=2C while other packages were noarch. Now it seems most of
 the packages are noarch. Was this intentional? It's a nice surprise=20
anyway if it is.<br>
<br>
- Nick 		 	   		  </div></body>
</html>=

--_db293c12-8a38-4a40-a418-2777b79f5e1e_--

Nicholas Kesick

Juan Hernandez

tags

participants (2)