From: Matthias A. <ma...@dt...> - 2004-06-26 10:48:06
|
Graham Wilson <bo...@de...> writes: > On Sat, Jun 26, 2004 at 02:11:24AM +0200, Matthias Andree wrote: >> I have taken this acinclude.m4 approach in bogofilter and am not very >> happy with that, updating individual macros is then more effort than >> necessary. I'd rather stick with a file per macro (or file per logic >> group of macros, call it module if you like). > > Do you mean that you'd have to search through the global file, rather > than replacing just a single file? Yes, that's exactly it. > If so, I'd rather go through that each time (I wouldn't think it would > be too often) rather than have a bunch of M4 macro files laying > around. I've found that solution to be impractical and would rather have a set of files lingering on the floor that I can nuke individually. > Additionally, can't the license file be added to the top of the macro > file, or to the COPYING file? That might be doable but makes the COPYING file a bit lenghty and cumbersome to read. > Sorry for being persistent, I would just like to keep the tree as > organized as possible. That's why I went with m4-local first :) -- Matthias Andree Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 |