On Apr 12, 2007, at 10:37 PM, Boey Maun Suang wrote:
As far as I can tell, however, work on base to allow for executing $ {build} in multiple directories would probably be necessary to deal with curlhandle and nefu, as well as with the dovecot-sieve plugin that I've been trying to write a port for. I haven't looked at the other two, but the dovecot-sieve source has been written on the premise that it will be extracted in a directory _adjacent_ to the main dovecot sources (i.e. ${blah}/dovecot-${version} and ${blah}/ dovecot-sieve-${version}), _and_ that that it will be build against the main dovecot sources _in the places in which the object files will be emitted by default in the dovecot build directory_. It seems like an awful lot of hacking on the Makefiles (which I'm not comfortable about doing just yet) would be needed to get dovecot- sieve to work without using [command build], either as a variant or as a separate port.
Instead of [command build] you could do what the build command would be doing... ie, system "cd whatever/ && make" It's not ideal (and probably base/ should be enhanced to have hooks so you don't have to do that sort of thing), but it doesn't involve using internal API.
If anyone can think of a nicer way of fixing the latter than by base allowing for the running of ${build} in multiple directories, I'm all ears (or eyes), but I can't see a better way of doing it.
-- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+