"manual" emerge/mutt/sasl

[diskmuncher]

I am trying to emerge mutt-1.4-r3. I have "sasl" defined in /etc/make.conf, but for this ebuild I wanted to not use SASL...so I did: "export USE="-sasl" (even though the mutt ebuild does not query the sasl USE variable and does appear to define --with-sasl in the econf section).

The emerge fails with:

checking for sasl_client_init in -lsasl... no
configure: error: could not find libsasl

!!! ERROR: net-mail/mutt-1.4-r3 failed.
!!! Function econf, Line 281, Exitcode 1
!!! econf failed

So...I edited the USE= in /etc/make.conf file to remove sasl (-sasl) dependence, and ran env-update. Same thing. I cannot figure out where/why it's picking up --with-sasl.

I can configure /var/tmp/portage/mutt-1.4-r3/work/mutt-1.4 by hand using all of the configuration options in the ebuild, and it configures/builds fine. I just can't remember how to emerge it without the recompilation step (I tried ebuild /usr/portage/net-mail/mutt/mutt-1.4-r3.ebuild install - but that wants to reconfigure/recompile)
_________________
John-David Childs (JC612) Enterprise Internet Solutions
Systems Administration http://www.nterprise.net
& Network Engineering WHOIS is your friend.
Direct replies to this email address are /dev/nulled.

[diskmuncher]

Just FYI...the answer to do this is (now) in the FAQ. unpack the ebuild in question, cd to the work directory of the extracted package (usually /var/tmp/portage/packagename/work), configure && make, touch /var/tmp/portage/<packagename>/.compiled and "ebuild merge" it into the system
_________________
John-David Childs (JC612) Enterprise Internet Solutions
Systems Administration http://www.nterprise.net
& Network Engineering WHOIS is your friend.
Direct replies to this email address are /dev/nulled.