./configure --prefix=/usr/local --enable-imap --enable-pop --enable-smtp --with-homespool=/var/spool/While I have satisfied my own needs, I feel I need the input of a seasoned linux user to ensure that I include the best all round compile options for greater usability. I'm very inexperienced with mutt

I will keep the compile options for future releases, as long as I am the maintainer.

./configure --prefix=/usr/local --enable-imap --enable-pop --enable-smtp --with-homespool=/var/spool/I've had a look through the mutt files after installing, and see that I have 3 extensions to releasemutt.tczmutt-doc.tczmutt-locale.tcz

I've been preparing lean extensions in what i think is the hard way, I install the package to /tmp/package and then remove what i don't need. If I'm releasing a core package, mutt for example, i'll remove the dir's that contain the doc and locale info. Then I run the relevant commands to make it into mutt.tcz then I clean up the /tmp/package folder, and run the mutt installer again, to get the doc and locale files back. Then I'll remove everything except the docs, so i can make that into mutt-doc.tczLike i said its slow and dumb. Can someone tell me the smart way to do it ?