You could rename ‘post.mk’ to something more unique and put the rest in an extra directory.

BTW I want to find a way to fix the requirement of passing -I to make. Maybe we will have to patch GNU make. We could do it using configure but I am pretty reluctant to go that route.

We moved to gnu make with small ./configure-scripts. That works fine on most modern unixes. A project like quagmire is something I had in my mind for a long time. Also, instead of using a Makefile.in we use a config.mk.in which we include in the main Makefile. All the @variables@ on a heap are much more readable.

(We tried scons, rake and cmake. cmake turned out to be ok. It generates makefiles as well. So make seems to be the common denominator which works really well).

Zack — thanks for the note. I will look at that.

Also I will try to get a real-ilfe example written.

Also I’d like to mention .po file generation and installation as one of the features that should be addressed sooner rather than later. It’s necessary for a lot of people, and the canned Makefiles and autoconf macros that come with xgettext are Drepper Quality Code, if you know what I mean? Thus good, trouble-free support for .po files could be a killer feature. Note that Monotone’s translators have been very clear that they do *not* want the .po files under version control to be automatically msgmerged every time the template changes — but that does need to happen for the built .gmo files. I don’t know if other projects’ translators are of the same opinion.

Nice to see this going forward. I particularly like the name — ‘quagmire’ just epitomises the muddy sinking feeling most of us feel about build systems!