Hi, Stefano :-). On Sat, 23 Aug 2003, Stefano Rivera wrote: >Just downloaded myself a copy of Binc 1.2.0b1 to take a look at it, >and while I am waiting for it to compile (on an old P-300) I thought I >would share my recent gripes with the bincimap build/install process. >1. There is no user-configurable logging dir, one has to go in and > hand-edit the service/log/run file.
I will add an option to configure, so you won't have to hand edit this file anymore. >2. During 'make install', the current bincimap.conf file is > overwritten with the new one. At the least, write it as > bincimap.conf.new, and notify the user to check for new > configurables. > Another option would be to read in the current variables and write > to bincimap.conf, saving the old conffile as bincimap.conf.old Yes, this is quite annoying. I will go for the first suggestion, avoiding the problems from users running "make install" twice. :-) >3. How about a 'make certificate' target for newbies to OpenSSL. Maybe > even a 'make ca' too? > I suppose that the distro should provide a Makefile in /etc/ssl, > but I know that Debian doesn't, I had to write my own. Good idea, this is certainly something we could do. >I solve 1 and 2 for myself with a patch that I apply to all new >bincimap downloads, but as Binc grows, so I will have to change my >patch - not very extensible. I can include this in the 1.2.0 version. I plan to add a couple of convenience features to 1.2.0 as we move out of beta development, such as checkpassword templates for several languages and better argument checking. >Bloody hell, it's still compiling... >I'll go and make some coffee. It's quite amazing how much slower g++ is than gcc, and especially in gcc 3.x (which is what I use). I drank so much coffee I had to switch to de-caf! ;) Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something | than to do it poorly."
