mkanat at bugzilla.org
Thu Aug 3 02:18:03 UTC 2006
Hey hey. So, checksetup.pl is basically a completely different file
than it was three or four days ago. Here's what you need to know:
Changes to the filesystem go in:
You'll see a subroutine there called FILESYSTEM that you can modify. If
you want to delete a file or directory, you can modify the
update_filesystem subroutine. You'll see that it already deletes some
things, just add your thing after that.
Changes to localconfig go into:
Adding a new variable is as simple as adding a new entry to the
LOCALCONFIG_VARS constant. All new vars must be scalars. (They can be
arrayrefs or hashrefs. They just shouldn't directly be arrays or
hashes.) If you remove a variable from localconfig, make sure to put it
into the OLD_LOCALCONFIG_VARS constant.
Changes to Bugzilla's required perl modules go in:
Changes to the database go into:
In particular, the update_table_definitions function. You'll notice
this function looks much nicer than the old checksetup code. Please keep
it that way! :-) Read the comment at the beginning of the function to
understand how it's supposed to work. You should also check out the
indicate_progress function if you're going to make the code do something
that takes a long time.
Settings now live in Bugzilla::Install.
All of the above files have POD, so you can read it.
checksetup.pl itself also has some good POD.
A few other changes will be happening. The initial creation of Groups
will move into Bugzilla::Install, the updating of fielddefs will
move...somewhere, and the creation of the admin will move into
Bugzilla::Install. Basically, any raw code in checksetup will move into
Competent, Friendly Bugzilla Services. And Everything Else, too.
More information about the developers