|
From: Donovan B. <ab...@mi...> - 2003-06-12 02:09:18
|
On Thu, 2003-06-12 at 11:51, Martin Pool wrote: > Rather than making the whole file autogenerated, I think it would > would be better to follow gtk and openssl in having a separate > librsync-config.h file which is generated from a .in file and included > by the main header. It seems a little easier to keep the > autogenerated stuff separate from the parts that people will generally > want to look at or change. Does this librsync-config.h replace the existing config.h? And rsync.h (now librsync.h) includes librsync-config.h? How does this impact on other projects that have their own config.h and include librsync.h? Don't you get similar sorts of problems? > I think I'd like to rename the file to librsync.h too, to reflect it > being separate from rsync proper. Sounds good to me. -- Donovan Baarda <ab...@mi...> http://minkirri.apana.org.au/~abo/ |