Packaging of Bugzilla 2.18 in Debian

David Miller justdave at
Tue Jan 18 19:43:45 UTC 2005

Alexis Sukrieh wrote:

> Well, the very first thing I need to do (and I have no choice here, else
> the package would not be Policy compliant), is to split CGIs from other
> scripts:
>     - quite everything go in /usr/share/bugzilla (less confusing than
>       the old package I think).
>     - *.cgi in /usr/lib/cgi-bin/bugzilla
>     - and the Bugzilla/ dir in /usr/share/perl5/Bugzilla

Not sure if this is a good place for the Bugzilla modules, since they're 
not official CPAN modules and are only used in Bugzilla. 
/usr/lib/bugzilla might be a better place for them.  On the other hand, 
putting them into the official Perl path means you don't have to fiddle 
with the "use lib" line in every file to get it to find them, so the 
patch is smaller. :)

> If this is an effort for you to change the way tempaltes work,
> nevermind, I can make a patch and keep it as a patch file. When building
> the package, the build process will then first apply the patch.
> That would allow us to keep the same source tree.
> The only thing I need to know is if this is possible only by patching
> the template files?

It should be possible to do something like [% webpath %] in front of the 
pathname to all of the images, js, css, etc files.  We can and should do 
this upstream, but I'd be happy to take that if you did it, since you're 
in the best position to test it.  The global template variable 
declarations in Bugzilla/ could get webpath added to it, and 
as distributed upstream, could just contain an empty string.  In the 
Debian distribution, webpath could changed with a one-line patch to be 
"../../bugzilla/".  This would let you set urlbase to 
"http://machinname/cgi-bin/bugzilla/" and everything would work.

> Moreover, I noticed that the CVS dirs and files are provided by the
> official 2.18 tarball. For the debian package to be lintian valid, CVS
> files must be removed. Is it necessary to keep them in the tarball?
> Using a cvs export can provide a nice tarball without the CVS stuff
> inside ;)

Yes, but it's very convenient to have those there as anyone downloading 
a tarball can then "cvs login" and "cvs update" to grab future updates 
if they have cvs available.  For people who customize their Bugzilla, 
this is a very attractive update option as it'll do some limited merging 
for you.

find $buildroot -name CVS -exec rm -rf {} \;

Dave Miller                         
System Administrator, Mozilla Foundation
Project Leader, Bugzilla Bug Tracking System

More information about the developers mailing list