gpgsm certificate validity

[yyy]

On 2011.08.23. 10:07, Werner Koch wrote:
> On Mon, 22 Aug 2011 18:05, yyy at yyy.id.lv said:
>
>> So, order of certificate hashes, relative of certificate order in
>> keyring, is critically important?
> No.  You need to make sure to not use lines of more than ~255
> characters.  Check that your editor didn't reflow a comment block or
> similar.
>
Re-tested today and it worked in more than one order. Probably issues in
yesterday were some sort of temporary glitch.

So, currently, importing a root certificate into gpgsm's keyring is a 2
stage process:
1. gpgsm --import _certificate_
2. edit trustlist.txt file, to add imported certificates hash (to make
it trusted (useable)).

For some certificates gpgsm asks during import, whether to trust them
(and if confirmed, add entry to trustlist.txt automatically). Is it
possible to make gpgsm to ask whether to trust it, for any certificate?