Problem is that, in case of a console-based browser, it is spawned immediately after the information message is displayed, giving no chance to the user to see it and then understand what's happening. This could happen during SSH sessions, or while inside a chroot.
Since 1.6.3, launchpadlib is able to determine whether user made her choice already, so a possible solution would be the following:
1) Display the info message
2) Ask user to push Enter/any key to spawn browser
3) Launch browser
4) Do the rest
This way, everyone is informed of what's happening, with a really small overhead of pressing a key.
Problem is that, in case of a console-based browser, it is spawned immediately after the information message is displayed, giving no chance to the user to see it and then understand what's happening. This could happen during SSH sessions, or while inside a chroot.
Since 1.6.3, launchpadlib is able to determine whether user made her choice already, so a possible solution would be the following:
1) Display the info message
2) Ask user to push Enter/any key to spawn browser
3) Launch browser
4) Do the rest
This way, everyone is informed of what's happening, with a really small overhead of pressing a key.