> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Saturday, December 16, 2000 1:01 PM > > > > When I originally wrote the buildexports stuff, we didn't require Perl to > > > build Apache, because that file could be generated once and just bundled > > > with Apache. With the move to create those files during the build steps, > > > we now require Perl just to build. I think the best solution is to move > > > that step back to the buildconf script, because that allows us to bundle > > > these files with the packages. > > > > Yes, that would eliminate the requirement for end-users. > > > > What about developers who want to test a CVS checkout of APR > > or Apache on a non-mainstream OS? Do you want to force them > > to install Perl? > > We expect that developers have access to a certain list of projects before > being able to build Apache or APR. I have no problem requiring Perl for > developers. I have a big problem requiring it for end-users.
So do I. So we may need to bundle a rewriter. We must choose something in an Apache compatible license.
