"After the baby was born, it took 6 months of medical treatment for her breasts to reduce back to their normal size."
Of course, what we all want to know is: HOW much did they grow?
3 posts • joined 10 Jun 2006
The apparent 'nonsense' is there to support what the apache source never has: automatically configured on install modules and the like. In, say, Debian land, it's not enough just having the main Apache package working out of the box, users also expect that installing php automatically enable the module, and installing squirrelmail adds the magic to enable them to use it out of the box.
And that's a bit of a bitch with a monolithic config file.
Apache's not the only package with this problem, the same war is raging over Exim4. Last I checked, the Debian package allowed you to choose between a monolithic config file, and one split into a lot of fragments (to allow, for instance, the mailman package to supply the fragment of configuration that it needs), which get assembled to a temporary config file when restarting the exim service.
As annoying it is to the hardcore Apache or Exim supporters, it's required to meet the needs that the distros fulfill in order to make the packages reach so many users as they have.
I don't see it as one side having to solve this problem, I think that distros and upstream supporters have to work together on it.
I think the important point is to preface examples with the right sort of disclaimer like 'this is not the proper way to do it, but I'll do for now' and that sort of thing.
I've set up a few PHP projects where, when I got to the "here's how you setup the database" part, I've thought "oh, no, that's not how I'm going to do it".
When a writer points out that he knows that it's not the 'correct' way to do something that I know something about, it makes me more confident that he'd do the same for the stuff I don't know about.
Biting the hand that feeds IT © 1998–2022