Malcolm Smith

Well, the [current NDK documentation](https://developer.android.com/ndk/guides/cmake.html) definitely recommends matching the `minSdkVersion`. If you can remember where you got that information then I'd be interested to see it.

If `OnUseNumber` was `public virtual`, then this could probably be fixed by adding a `__namespace__` attribute to the Python class, as in https://github.com/pythonnet/pythonnet/issues/567#issuecomment-341960560. However, based on [this discussion](https://mail.python.org/pipermail/pythondotnet/2016-September/001820.html), overriding `protected...

> There's a whole load of corner cases / unusual usages that would have to be considered (upgrades, ``--target``` installs, for example) In the case of `--target`, things are even...

> The package manager, pacman, [...] does refuse, by default, to let one package overwrite files already present in the system. Conda [has the same policy](https://conda.io/docs/user-guide/tasks/build-packages/define-metadata.html#specifying-files-to-include-in-output).

A similar segfault occurred due to some missing `retain` calls which were added by [this commit](https://github.com/beeware/toga/pull/2075/commits/69e760b6d707871215b0ea2cf6cdc3dc383e7449).

> My initial idea is to just add an additional `release` call whenever such objects are deleted on the Python side Alternatively, how about this? * Call `retain` when the...

There are also some type methods that don't follow the naming convention, like `NSURL.URLWithString`. As I understand it, the Rubicon user must manually `release` the object returned by such methods....

> there's an implied `retain` already on any object you create - so, any `alloc`, `new`, etc method will either require an additional `release`, or _avoid_ invoking `retain` on every...

> I think the `retain()` calls aren't actually needed in those cases - they just need to be `autorelease()` ~~I think they are needed with the current implementation: see https://github.com/beeware/toga/pull/2482.~~...

> as I understand it, `NSURL.URLWithString` falls under the "owning an object you create" clause - i.e., the "alloc, new, copy..." list is indicative, but isn't exhaustive; class-level "create and...