William A. Rowe, Jr. wrote:
Folks you are talking over each other.
Why not simply ./automake and check in the resulting ./autoconf-ready
files? If you desire to delete the automake files afterwards, th
...at's fine. It's how we migrated the incubating mod_ftp out of automake.
Of course more work on mod_ftp's build system is still needed, but at least
automake is out of the picture.
[dang touchpad mousebuttons under my wrists lol]
Bill
Paul Querna wrote:
Justin Erenkrantz wrote:
On 2/11/06, Paul Querna <[EMAIL PROTECTED]> wrote:
If you really want me to revert it I will. Then we won't have any
build
system at all.
Maybe you are forgetting what we had before. A single makefile with
paths hard coded for your home directory.
build-dso was the 'build' system - not Makefile.
If you want to convert it to use httpd's build system, no one is
stopping you.
How? svn copy into a branch, make the changes, commit it, tell
everyone, merge the branch.
FWIW, Automake doesn't require everything to be in src/, but it seems
you are so tainted against the tool (Hey, I don't exactly love it
either), that it doesn't matter that it currently _does_ work.
We shouldn't be releasing code that has a dependency on automake. --
justin
Please define dependency.
We have a buildconf dependency on Python in httpd. configure doesn't.
Automake is the same as Python in this case.
