Development repository

[Michael_E_Brown at Dell.com]

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.

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.
--
Michael

-----Original Message-----
From: Orion Poplawski [mailto:orion at cora.nwra.com]
Sent: Tue 4/15/2008 1:59 PM
To: Brown, Michael E; firmware-tools-devel at lists.us.dell.com
Subject: Re: Development repository
 
Michael_E_Brown at Dell.com wrote:
> Orion,
>     Rawhide is always very hard for me to support, because I have to do a full rebuild of all RPMS for each beta. This doesnt fit into my model for posting things to the repo at all, and I usually only update rawhide on an 'as-I-have-time' basis, which has been extremely scarce lately. I dont have any good answer for this atm, as I dont see a good way to script these updates, and I dont have the cycles to manually kick these through right now. :(
> 

Why do you need to rebuild your RPMs?  Looks like most are very simple 
noarch which should work from release to release.

-- 
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