bugzilla rpm (was: Summary of comments on Slashdot article)

Axel Thimm Axel.Thimm at ATrpms.net
Tue Dec 7 17:14:21 UTC 2004

On Mon, Dec 06, 2004 at 03:54:08PM -0500, Christopher Hicks wrote:
> On Mon, 6 Dec 2004, Axel Thimm wrote:
> >I also have a (yet non-public) bugzilla rpm (currently at 2.18rc3), but 
> >I'm quite unhappy about its post installation scripts (it creates a 
> >default bugzilla instance).
> If you can share it I'd be willing to work on it.

OK, I shoved it into the bleeding repo. don't use it on a box that
already has a working bugzilla instance. Patches are welcome!


> >All it _should_ do is store bugzilla into /usr/share/bugzilla waiting 
> >for someone to copy it over to /srv/<project>/bugzilla. Perhaps with a 
> >smart bugzilla-create-instance script that also creates the database and 
> >sets in database and localconfig a randomly chosen password.
> That's similar to my plan, but I want each instance to be installed from 
> rpm by changing the prefix each time.  This way (as I understand it) it 
> would allow each install to be upgraded when the repository upgraded. 

You mean relocation? You still cannot install multiple packages, they
will have the same NEVRA.

> We're doing a few bugzilla hosts now for various folks and I'd be a lot 
> more active at keeping everybody up to date if I could do it with yum.

This cannot be solved on the packager level, you could have a script
that updates the bugzilla instances under /srv/*/bugzilla and have
that script in the %post script of rpm.

But the better plan is to separate code from data and have all
bugzilla instances use code from $datadir/bugzilla. That way an rpm
update will indeed update all you instances (for better or for worse!)
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20041207/7a888b1f/attachment.sig>

More information about the developers mailing list