Russell Keith-Magee

> I'll need to assess all this more fully....but a different perspective may not consider this as confusing. For sure - interpretation matters a lot here. Making the situation impossible...

> With the changes proposed here, Briefcase will instead (strive to) _always_ keep the bundle up-to-date with the sources of truth and will require explicit instruction from the user to...

> So, please let me know if you see holes in this algorithm. That seems fine to me. It will definitely catch the obvious cases, and if there's any common...

> I guess not so surprisingly...understanding if something changed inside a directory is becoming full of corner cases. > > If we just consider the app sources, this should be...

> As a preliminary speed test, I created a `sources` directory with 100,000 files in it. On a beefy system using an SSD, it calculated the hash for that directory...

See #1733 for a related edge case that might need to be detected: has the venv itself changed? The datestamp on the `python` executable might be a reasonable proxy for...

> Along with this, I've implemented the heavy hitters for this so far: > * Briefcase version changes How sensitive is this to dev commit-level "version change" updates? > *...

> > > Along with this, I've implemented the heavy hitters for this so far: > > > > > > * Briefcase version changes > > > > >...

As I indicated in #213 - even if this *can* be rewritten in terms of a `curl` call, I'd suggest its a *really* bad idea to do so. There are...

Requested by @nedbat on Mastodon: If you want an example of this in practice: Briefcase has an extensive set of Python version and OS conditional coverage definitions, with coverage merging...