New lifecycle idea

[mmalecki]

Current lifecycle management is broken (for example, #82, #90). So, here's a proposal for new cycle:

• only differentiate if a system is installed or not - don't rely on exact history to determine which script was ran (so, if you run install on a system which is installed, it'll fail, same for uninstall)
• don't fetch new system version automatically - instead require user to quill upgrade it explicitely
• when system is upgraded (not updated - update is a lifecycle script, not lifecycle action), uninstall on the old version is ran and install is ran on a new one (those could be different scripts too, e.g. pre-update and post-update).
• configure, update or start call install implicitely, if the system isn't installed.

I feel like this is more intuitive.

/cc @indexzero @jcrugzz

[jcrugzz]

I agree the current lifecycle management is broken. Let me respond to each of these points individually.

1. Yea the exact history does not seem necessary.
2. I can see upgrade and update possiblt being confusing. npm install has the same behavior of quill install except its usually referencing the package.json rather than installing the newest. The distinction to force the uninstall on upgrade may be worth it though.
3. Totally agree with the last piece, install should be a basis for all those lifescycle events.

[mmalecki]

Right, naming of upgrade and update is a problem. Let's break this up for multiple package managers:

• yum, npm - upgrade and update mean all the same
• pkgin, apt-get, brew - update means "update all the new metadata", upgrade means "upgrade actual software"

This makes me think that we could actually use update for the system update and upgrade for software update (as the lifecycle script). Thoughts?

[yawnt]

i've always hated this differentiation
.. something like sync for meta and up(grade|date) sounds better imho

[jcrugzz]

@mmalecki also by removing this history portion we will be able to add a stop lifecycle event as well correct?

[mmalecki]

@jcrugzz lifecycle script, but yes.

[indexzero]

@mmalecki lgtm. Make sure all the tests pass and hopefully add more test coverage

[jcrugzz]

so i think we should keep update and have that one automatically install new version. It would be more consistent with what we expect currently, but we do need a new word. I don't HATE sync, but I think there might be something better.