automatically update requirements.txt file after each (un)install command
let the developer to update the file and call vip --update each time (s)he does this
In favor of (1) is the reason to keep everything simple, but explicit is better than implicit.
Option (2) is explicit which is good. In addition to (2), requirements.txt.lock can be created in order to list all used packages (similar how bundler does in Ruby).
There are two options:
requirements.txtfile after each (un)install commandvip --updateeach time (s)he does thisIn favor of (1) is the reason to keep everything simple, but explicit is better than implicit.
Option (2) is explicit which is good. In addition to (2),
requirements.txt.lockcan be created in order to list all used packages (similar how bundler does in Ruby).