simonbaird/mGSD

For each release, create an update file that contains only the tiddlers that have changed since the last release

Opened this issue · 3 comments

simonbaird commented

This would assist people who's customisations are regularly clobbered unnecessarily by updates and also reduce needless download/importing of unchanged tiddlers.

damo commented

This would be an improvement, but it would not help if I have customised one of the updated tiddlers. Is there a way I could check in advance which of my customisations will be clobbered by an upgrade? That might require detecting that I have made a change.

Jobirder commented

I don't see this as feasible. Imagine the following:

A user starts with mGSD at point A.
Updates are published for A-->B.
Updates are published for B-->C.

User "A" decides to update to C. They are now faced with two bad options: Run the update designed for B-->C (which may break things and generally not work) or import the full mGSD (thus losing MORE of their own tiddlers).

simonbaird commented

@damo It might be possible. A generated report could be made. Maybe even a link to the applicable diff on git hub would be better than nothing.

@kralik, true. But they could run the upgrades one after the other.