this would necessarily trigger a new rebuild for something that already exists.
And you want to avoid this because? :-)
Apart from the resources question (CO2 etc), it looks like it could create a strange release numbering. Assuming we start off like this: Project "openfoam" with that generates - openfoam-<version>-<release> (meta package) - openfoam<api>-<version>-<release> (payload package) With some concrete values: - openfoam-2012.210414-lp152.4.3 <rpm> - openfoam2012-2012.210414-lp152.4.3 <rpm> To "archive" them, I would presumably spinoff my archive project as "openfoam2012" and copy/rename the spec file. Since this would be a new project, it will presumably have its own internal release numbering. Eg, would now create these: - openfoam-2012.210414-lp152.1.1 <<-- new accounting - openfoam2012-2012.210414-lp152.1.1 <<-- new accounting Not sure I would have to wait for these to be generated and published before moving on, but I could then proceed to edit the "openfoam" project to bump to a new major version etc. However, I make any minor build/spec tweaks to the "openfoam2012" archived project, it could take a while until it finally overtakes the older release version. Could be confusing to say the least. Or am I misunderstanding something fundamental about how the build system works? Cheers, /mark