Installation should not be interactive

[Mikael Blomstrand]

Building a package with makepkg is not supposed to be interactive, let alone set up configuration. It would be slightly better to have this in a post install script, but it really should be completely separated from the installation process.

(This is the same issue as Ventto/pug#6)

[Derek Brown]

@mbloms what would you suggest as an alternative?

[Mikael Blomstrand]

One way would be to ask the user for login first time using the program. Or ask them to put it in a config file manually. Some users (me included) could probably be off put by having to supply password at all instead of just supplying an access token manually. gist stores it's access token in ~/.gist. Maybe use the same file? (Though putting it in ~/.config/gist is probably cleaner.)

[Derek Brown]

So, we can't ask them for a password the first time they use the program for the same reason you cite we can't ask them when they install. Pacmanity is called as a program hook, so it is not supposed to be interactive.

We could manually force users to authorize the gist module, but this honestly seems like a bad tradeoff; I would rather break convention and have an interactive setup than have a completely manual setup.