unison formal review
Dominik 'Rathann' Mierzejewski
dominik at greysector.net
Thu Sep 29 16:50:04 UTC 2011
On Thursday, 29 September 2011 at 15:38, Jesse Keating wrote:
> On Sep 29, 2011, at 1:13 AM, Garrett Holmstrom wrote:
> > One build could produce a package for each version. The packages'
> > n-v-rs could then be maintained independently. I am not sure how bodhi
> > would behave in such a case, though.
> > This most certainly is not optimal; I'm simply throwing the idea over
> > the wall.
> The build system would reject this. Every produced rpm has to have a unique n-v-r.
One solution would be to make per-version subpackages conditional via macros
and build only the one that has been updated.
Example: we have unison-2.9-1 package which produces
We want to update unison28, so the next build of unison-2.9-2 produces only:
What do you think?
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
-- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
More information about the devel