Hello,
I found that there is actually a prebuilt 4.8 context RPM in one of their
source trees (not GitHub).
As per the repo change, this new version actually makes more sense and
follows proper repo format.
http://mirrors.kernel.org/centos/6/os/x86_64/ being an example repository
that follows standard format.
The "stable" path part didn't make any sense considering how versions work
in OpenNebula.
On Mon, 25 Aug 2014 15:46:37 -0700, Bill Cole
<openneb-users-20120...@billmail.scconsult.com> wrote:
Past OpenNebula 4.x releases have been packaged as RPM's for CentOS
available in a yum repository with a baseurl of
'http://downloads.opennebula.org/repo/CentOS/6/stable/$basearch'
For some inscrutable reason, 4.8 RPMs are not there. Instead, the 4.8
docs on the website now direct us to a repo at the baseurl
'http://downloads.opennebula.org/repo/4.8/CentOS/6/x86_64/'
Is there a rational explanation for this? One of the main points of
using a package management system like yum/RPM is to simplify updates,
but this change obfuscates the visibility of the update and seems to
indicate a plan to hide future releases as well.
Also, the new repo lacks an RPM for opennebula-context and the release
notes point to a github repo which includes a script to build packages
from the source. Does this mean there will no longer be a prebuilt RPM
of opennebula-context?
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
