Re: unison formal review

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
unison-2.9-1
unison28-2.8-2
unison21-2.1-5

We want to update unison28, so the next build of unison-2.9-2 produces only:
unison28-2.8.1-1

What do you think?

Regards,
Dominik

-- 
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org | MPlayer http://mplayerhq.hu
"Faith manages."
        -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux