Hi there,
this patch provides the capability to configure whether only the latest build of a package tagged with <tag> should be included in the mash, or whether all builds of a package tagged with <tag> should be included (and thus be available in the repository).
-- Jeroen
Jeroen van Meeuwen (kanarip@kanarip.com) said:
this patch provides the capability to configure whether only the latest build of a package tagged with <tag> should be included in the mash, or whether all builds of a package tagged with <tag> should be included (and thus be available in the repository).
I don't see anything functionally wrong with the patch. It's going to wreak havoc on deltarpm creation depending on the size of the repo, though, if deltas are configured.
Applied.
Bill
On 01/11/2010 06:07 PM, Bill Nottingham wrote:
Jeroen van Meeuwen (kanarip@kanarip.com) said:
this patch provides the capability to configure whether only the latest build of a package tagged with <tag> should be included in the mash, or whether all builds of a package tagged with <tag> should be included (and thus be available in the repository).
I don't see anything functionally wrong with the patch. It's going to wreak havoc on deltarpm creation depending on the size of the repo, though, if deltas are configured.
Applied.
Thanks.
I recon that the delta foo is going to be a lot, lot more exhausting in the case where you use latest=False and deltarpms, but for downstream buildsystems and mashups (which is the use-case here), I doubt the use of deltarpms is going to be a requirement (and if it is, well... :P).
-- Jeroen
buildsys@lists.fedoraproject.org
-
Bill Nottingham -
Jeroen van Meeuwen