Eric Smith wrote:
> I've seen that done, but didn't know the purpose. I think it's the
> right case in my situation. I've updated muParser in rawhide, and am
> pushing updates for F16 and F17. muParser has a new so version.
> Meshlab depends on muParser, but meshlab currently won't build in F17
Bruno Wolff III wrote:
Rawhide inherits from updates of the most recent branch, which is
currently the branched release (f17). Updates will inherit from the
release. A package is only inherited if there are no builds for it at
the current level.
[and more good explanation]
Thanks! That's ex
On Sat, Mar 10, 2012 at 02:14:50 -0800,
Eric Smith wrote:
> The "Join the package collection maintainers" page gives the warning:
>
> I've never really understood that, but it's never previously caused
> me any concern. Since I am now in a situation where I want to push
> an update to a branch
The "Join the package collection maintainers" page gives the warning:
Be sure that you build for rawhide (master) branch before pushing
updates for any other branches! Otherwise, those updates will get
inherited into rawhide, which is almost certainly not what you want.
I've never really unde
