// I've added a check that the /system version ("0.1.0d") matches what the binaries expect; otherwise there's no limit to how weird the bugs can be caused by mixing versions. If you are maintaining your own hacked /system, you can get rid of the warnings by just "about /system" to edit the version to match.
~but then.. remember not to report any bugs unless they also show up on vanilla picotron o(_ _)o
@zep hey zep! great stream of updates for lovely picotron :)
sorry to bring this up but: we are encouraged to read system code to understand things, we can copy apps and try edits, then we share code snippets and sometimes the edited apps. but what is the license for them? are we allowed to share snippets / diffs / edits?
@merwok hey :)
There is currently no license! I'm fine with sharing snippets diffs & edits, but still working on formalising that. Ideally there would be a single simple license that covers (most of) /system, exports and later the c runtime source. The challenge is to do that in a clear way that allows creating tools/makers etc similar in nature to Picotron, but without functionally duplicating [large parts of] Picotron itself.
Add comment