Re: Upcoming changes in mod_mbox repository

2006-02-15 Thread Justin Erenkrantz
On 2/14/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: > Otherwise, I'd like to have some more detailled explanations (or a mail > reference to) on this veto. http://mail-archives.apache.org/mod_mbox/httpd-mbox-dev/200504.mbox/[EMAIL PROTECTED] HTH. -- justin

Re: Upcoming changes in mod_mbox repository

2006-02-14 Thread Maxime Petazzoni
* William A. Rowe, Jr. <[EMAIL PROTECTED]> [2006-02-11 17:10:36]: > >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 cou

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Maxime Petazzoni
* Maxime Petazzoni <[EMAIL PROTECTED]> [2006-02-12 01:50:38]: > Expect for the automake problem, I already made the necessary changes > to the surgery branch to comply with justin's will (aka not having an > src/ directory and renaming data/ to docroot/). s/Expect/Except/ Too late out there, nee

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Maxime Petazzoni
Hi, * Maxime Petazzoni <[EMAIL PROTECTED]> [2006-02-10 01:22:22]: > Before releasing mod_mbox, we need the work done in the surgery branch > back to trunk. So, unless there is any objections to it, here it what > I'll do in the next few days : > > - Move the scripts/ directory one level up, out

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread William A. Rowe, Jr.
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

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread William A. Rowe, Jr.
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 Bill Paul Querna wrote: Justin Erenkrantz wrote: On 2/11/06, Paul Querna <[EMAIL PROTECTED]> wrote: If you really wan

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Paul Querna
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 '

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Justin Erenkrantz
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

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Maxime Petazzoni
* Justin Erenkrantz <[EMAIL PROTECTED]> [2006-02-11 11:53:40]: > automake doesn't work. The solution is to revert Paul's commit that > introduces automake. (Paul should really be the one doing this - not > you - since he started this mess and promised that he'd revert it way > back when.) > > I

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Paul Querna
Justin Erenkrantz wrote: On 2/10/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: Okkaay. Please read again my paragraph. Now please read the STATUS file. The current automake setup *works*, and migrating to the same build system than httpd is planned. If you don't want any mod_mbox release to go

Re: Upcoming changes in mod_mbox repository

2006-02-11 Thread Justin Erenkrantz
On 2/10/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: > Okkaay. Please read again my paragraph. Now please read the STATUS > file. The current automake setup *works*, and migrating to the same > build system than httpd is planned. If you don't want any mod_mbox > release to go out until I find an

Re: Upcoming changes in mod_mbox repository

2006-02-10 Thread Maxime Petazzoni
* Justin Erenkrantz <[EMAIL PROTECTED]> [2006-02-10 21:54:27]: > On 2/10/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: > > It works, in a very simple and common way, and changing the build > > system is not (yet) part of the showstoppers. Please keep in mind that > > I want this release to be so

Re: Upcoming changes in mod_mbox repository

2006-02-10 Thread Justin Erenkrantz
On 2/10/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: > It works, in a very simple and common way, and changing the build > system is not (yet) part of the showstoppers. Please keep in mind that > I want this release to be some kind of out-of-SoC release, not a > mod-mbox-has-become-the-killer-mo

Re: Upcoming changes in mod_mbox repository

2006-02-10 Thread Maxime Petazzoni
Hi, * Justin Erenkrantz <[EMAIL PROTECTED]> [2006-02-10 07:54:49]: > Can you please consider removing automake? (I did -1 it when Paul > committed automake the first time.) If you feel brave enough to get a hand on the new build system, feel free to do so. Personally, I don't know how it works,

Re: Upcoming changes in mod_mbox repository

2006-02-10 Thread Bill Stoddard
Justin Erenkrantz wrote: On 2/9/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: Recently, I've been working on cleaning up the directory structure of the module's source code in a 'surgery' branch. Today, this work is done and the branch's code compiles, installs and works fine here at home. Ple

Re: Upcoming changes in mod_mbox repository

2006-02-10 Thread Justin Erenkrantz
On 2/9/06, Maxime Petazzoni <[EMAIL PROTECTED]> wrote: > Recently, I've been working on cleaning up the directory structure of > the module's source code in a 'surgery' branch. Today, this work is > done and the branch's code compiles, installs and works fine here at > home. Please not that the fun