xulrunner 2.0 in rawhide (F15) bundles several system libs

[Kevin Kofler]

Christopher Aillon wrote:
> I personally don't care what we call it.  I'm not going to start
> breaking funny cat videos

You shouldn't break the videos, you should apply the Debian patch to use the 
system libvpx, then the videos will just work.

> just to meet packaging ideals on a deadline. I'd rather deal with all you
> guys complaining on fedora-devel and in fesco tickets than the influx of
> bugs if I started breaking shit.  It's bad enough that there are more bugs
> than we can handle.

Then you should be replaced by a maintainer who actually cares about our 
packaging guidelines.

> Besides, Mozilla has a good track record of allowing system libs after
> things settle down, and I have no doubt that we'll get these at some
> point.

That's too late. The libraries MUST NEVER be bundled, at NO point in time.

>  From Mozilla's perspective, they could:
> 
> 1. Do what they are doing now, temporarily not allow a few new system
> libs, waiting until they get banged into shape and *then* enable system
> libs (down the road).
> 2. Bang on the code in private and wait until it meets every Fedora
> packaging guideline, etc, until committing to the upstream repository,
> so we all get to wait for all of the cool shit that's happening.

3. Just allow distributors to build against the system libraries and trust 
them to know what they're doing!

They're the ONLY upstream which makes it such a PITA to ship their project.

> Please note that we're talking about pre-release versions of Firefox in
> a pre-release version of Fedora anyway, so a lot of churn is to be
> expected.  We're almost certainly going to have to temporarily disable
> and reenable a lot of other system libs during the beta cycles to get
> builds out the door, just like we always do in rawhide.

This is not acceptable.

> Not that I can guarantee that the release version will have all the above
> system libs enabled, but we'll know a lot more closer to FF4 and F15
> release time.

And neither is this.

We have policies for a reason, Firefox must stop being "special" and start 
following the same rules as everyone else.

        Kevin Kofler