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

Followup to FESCO meeting: firefox dependancy tracking.

As per the FESCO meeting item list, and irc discussion, here is my
humble attempt to identify via repoquery what packages are currently
prone to library dependancy breakage without being noticed by the
automated scripts which just look for rpm autogenerated library

these are packages which have a requirement on a library from firefox,
but do not explicitly require firefox or gecko-libs:


If you just look at packages which do not use a versioned firefox dep
you also get:


The only packages which use a versioned firefox requirements are:


My suggestion is that all packages which end up requiring a library
from firefox should use a versioned dependancy as long as firefox
continues to keep its libraries in a versioned directory tree (
currently  /usr/lib/firefox- ). If a versioned firefox
requirement is used we can atleast become aware of breakage as it
happens via the available infrastructure scripts. As it stands the
majority of the packages which depend on libraries from firefox will
have library breakages on firefox updates and we can't see them from
the available rpm dependancy information. Users will hit this issues
when the library linker goes looking for a library in the wrong place.

Comments?  Should I start filing bugs against these packages to get
versioned firefox requires added to their specfiles?  Should we look
at making this sort of thing part of the review process that should be
checked for?

Note that my use of repoquery still doesn't catch problematic packages
like gnome-python2-extras nor esc which do not have trackable rpm
library dependancies for repoquery to work with.


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