Re: mmc patch
Cory Wright <cwright-dated-1044057964.281861-fBYJ9vZApKkqcZcGjlUOXw@public.gmane.org> Sun, 26 Jan 2003 19:06:03 -0500
| Newsgroups | gmane.comp.lang.moto.devel |
|---|---|
| Organization | Stand Blue Technology |
| Message-ID | <[email protected]> |
On Sun, Jan 26, 2003 at 05:33:54PM -0500, David Hakim wrote: > Cyb.org recently sent me a patch for mmc that includes a new -i > command line option. Only when the -i option is passed will mmc install > the compiled DSO into the apache libexec directory. If the -i option is > not passed than the DSO is copied to the current directory. What do > people think of this ? I'm a little worried because it changes existing > behavior ... but not in a large way. I also remember there had been a > discussion at one time of moving compiled DSOs to whatever directory > mod_moto.so was installed in. > > Thoughts, comments ? I think this is a terrific idea. Installation should only be done where explicitly indicated. This is actually one thing that I have always found annoying about compiling new modules. What would be nice is if it could be run in a similar fashion to 'make', or even use 'make' so that a new module would only be compiled if there were changes to the code that is about to be compiled. Something like this would make it easy to compile first, then install when ready: mmc -n mysite /home/mysite mmc -i -n mysite /home/mysite A 'make'-like approach could be handy down the road if people start using Moto to build really large sites with lots of code. Just my thoughts, Cory -- Cory Wright Stand Blue Technology http://www.standblue.net/