69747 - Proper packaging support.

Status: RESOLVED INVALID

(Bugzilla :: Bugzilla-General, enhancement, P2)

Description

[Matthew Tuck [:CodeMachine]]

IMO one of the aims of BZ3 should be proper packaging.  By this I mean
separating out everything to where it should really go.  Our priorities should
be:

(a) Nothing should be in the WWW tree unless it needs to be, ie .cgi, .html and
images.  No data directory, no shadow directory, etc.  This will remove the
possibility of many of the security holes we have seen.
(b) We should make it reasonably easy for distributions to package Bugzilla,
though I'm not sure exactly what this means.

Here's my suggestion:

www - Directory containing all stuff to go in the www tree.
docs - Admin documentation not going in the WWW tree, such as Bugzilla FAQ.
contrib - As before.
bin - Programs for administrator to run (checksetup, syncshadowdb).
lib - Place where all supporting code goes (.pl files that get run by .cgis),
which would be nice to move out of WWW in case the web server is set up to let
users run them.

We also need a place to put data, presumably /etc/bugzilla & /var/*/bugzilla.

We would need to make sure all the code supports these new locations, whether
ornot they are hardcoded, and that's why we should do this as a part of 3.0.

We might want to make this easily supportable on Windows machines, by keeping
the locations configurable and doing something about the path separator.

Comment 1

[Dave Miller [:justdave]]

Moving to real milestones...

Comment 2

[Hixie (not reading bugmail)]

Taking all Bugzilla 3.0 bugs -- congratulations to MattyT for the triage, it
really was spot on. Note: I may end up pushing some of these bugs back to 3.2,
we'll see. However, I believe all these bugs should just fall out of the 
redesign. Let's hope I'm right!

(Note: I'm also resetting the priority field to "---" so that I can retriage any
that I consider important or likely to be dropped.)

Comment 3

[Dave Miller [:justdave]]

The Bugzilla 3 component is going away.  We're going to depend on the Milestones 
for this.  At the time this component was created, we didn't have milestones for 
Bugzilla.

Comment 4

[Hixie (not reading bugmail)]

Bailing on Bugzilla 3.0 due to too many other commitments.

Comment 5

[Max Kanat-Alexander]

Modern Bugzilla is organized much better, and supports moving things around by editing Bugzilla::Constants::bz_locations.

Although I wouldn't say this bug is fully WORKSFORME, I would say it's not totally relevant anymore. The only thing we have left to do is actually make "$libpath" work, and I think that would be a separate bug.