Michael_E_Brown at Dell.com wrote:
> Except it isnt always that simple. Rawhide sometimes has API/ABI breakage from release to release, so there are no guarantees that packages will work from beta to beta. For example, iirc perl had a major upgrade between betas.
>
True, but you'll have to deal with it at some point. My take would be
simply duplicate the previous release repository until problems are found.
> In any case, even without having to recompile, the way that rawhide does it's release rpm makes it also hard to keep up with all of the builds, because the repo name keeps changing.
Well, you could just avoid the whole rawhide beta version numbers and
skip to the upcoming release number:
--- bootstrap.cgi 2008-04-15 09:17:36.000000000 -0600
+++ bootstrap.cgi-devel 2008-04-16 11:46:24.000000000 -0600
@@ -101,7 +101,7 @@
fi
if [ -n "${FEDORA_RELEASE}" ]; then
- VER=$(rpm -q --qf "%{version}\n" ${DISTRO_REL_RPM})
+ VER=$(rpm --eval %fedora)
dist=fc${VER}
elif [ -n "${REDHAT_RELEASE}" ]; then
VER=$(rpm -q --qf "%{version}\n" ${DISTRO_REL_RPM})
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion at cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com