[Bug 188359] Review Request: bugzilla - bug tracking tool

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: bugzilla - bug tracking tool


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188359





------- Additional Comments From tibbs at math.uh.edu  2006-06-20 15:18 EST -------
I thought rpm would pull versioned dependencies out of a "use Module VERSION"
statement.  It won't find them any other way as far as I can tell.  In the case
of this package, all of the module dependencies are unversioned.

If the necessary versions were provided in base FC4 or the oldest version ever
in extras then we're OK.  Otherwise then there is the possibility that someone
who has never done any updates might have an old module installed, so we'd have
to include versioned dependency information.

If we can get away with doing so for a couple of modules then it might not be
too bad.  But if not, it's probably easier to just turn off RPM's dependency
generation altogether and just supply a list.  It shouldn't be too hard to hack
checksetup to dump a dependency list in the proper format and then just call it
in place of the regular perl dependency generator.

One additional thing bothers me.  rpmlint has this complaint:

E: bugzilla file-in-usr-marked-as-conffile /usr/share/bugzilla/localconfig

We cannot assume that anything under /usr/share is writable except at install
time, so it's really not the best place to put a config file.  I looked through
the source and it does look like it expects the configuration to live in
$libdir.  However, this seeps to be specified in only one location,
Bugzilla::Config.pm, so it should be possible to patch two lines and get it to
look in /etc/bugzilla instead.  Do you think this is feasible?

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.