Closed Bug 105854 Opened 23 years ago Closed 18 years ago

Create Configure.pl script for Bugzilla

Categories

(Bugzilla :: Installation & Upgrading, enhancement, P2)

2.15
enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: zach, Assigned: zach)

References

Details

Have a configure script which looks at various config info, tries to figure things out, and asks questions (but has a defaults mode for cronjobs to run non-interactively). Once the questions have been asked, it generates a Makefile and other config files.
cc'ing all cc's from the meta bug
Blocks: 44659
Ok, we have a configure system designed to do what we need for now. The only problem is that it does nothing useful since we have no questions at the moment (since we need to know what the questions are...). Right now it has all the hooks and API foo (Conf.pm) and outputs a file with the configuration to load defaults into later and parses a Makefile.in into a Makfile. All vars like **somevar** become whatever somevar was set to in Configure $main::c{somevar}. It still has some issues, doesn't use strict, etc, but that will be dealt with in due course. The important thing is that we now have a stable enough configure platform to let the Configure Scene come to a close and let the Makefile.in Scene begin. When the Makefile people (which I am NOT NOT NOT (I am Makefile challenged) need Configure input, they can post the question here and I will add that to configure. --Zach
Ok, we have a configure system (on the branch, bugzilla_newinstall) designed to do what we need for now. The only problem is that it does nothing useful since we have no questions at the moment (since we need to know what the questions are...). Right now it has all the hooks and API foo (Conf.pm) and outputs a file with the configuration to load defaults into later and parses a Makefile.in into a Makfile. All vars like ** somevar** become whatever somevar was set to in Configure $main::c{somevar}. It still has some issues, doesn't use strict, etc, but that will be dealt with in due course. The important thing is that we now have a stable enough configure platform to let the Configure Scene come to a close and let the Makefile.in Scene begin. When the Makefile people (which I am NOT NOT NOT (I am Makefile challenged) need Configure input, they can post the question here and I will add that to configure. --Zach
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
*** Bug 109312 has been marked as a duplicate of this bug. ***
Blocks: 147776
I made pretty good progress on Configure.pl, Conf.pm and friends during my escape to Australia. I think I'll make a new branch and land those changes there in the coming week after I get some bugs worked out. Also, I need to get some more details about newinstall out for comments. Don't worry, this hasn't been forgotten. Stand by.
We need to fix 171674 (File::Temp and 5.6.0) in newinstall as well. If you haven't yet, check out the newinstall branch: things are happening. cvs -z3 co - d bugzilla -rbugzilla_newinstall Bugzilla
Depends on: 171674
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being retargeted to 2.20 If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Wow... now what ever happened to *this*? I don't fully understand what sort of improvement this is over checksetup, from the comments here on this bug.
Severity: normal → enhancement
OS: other → All
Hardware: Other → All
Summary: Create configure script for bugzilla → Create a script that deals with all configuration details
This is/was a tracking bug for newinstall, a new (perhaps stalledinstall would be a better name though) installation system which uses the more normal "Configure.pl && make && make test && make install process" and many other improvements. Of course, someone needs to actually finish this system, but that's what this bug is from.
Summary: Create a script that deals with all configuration details → Create Configure.pl script for Bugzilla
Ahh. For the record, I don't see the advantage of using a Makefile install. :-) Makefiles are complex nightmares, used for compiling code and dependencies. Perl is nice for the sort of stuff that we need to set up and configure. Also, more of the developers understand and can use Perl, making it much easier to modify a wholly perl-based installation system. From what I can see, in fact, newinstall stalled partly on the fact that nobody had Makefile skills.
I vote to WONTFIX this, at this point.
Target Milestone: Bugzilla 2.20 → ---
QA Contact: mattyt-bugzilla → default-qa
I suggest WONTFIX too. checksetup.pl is working really well; it doesn't make sense to restart from scratch.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.