updater issueshttps://gitlab.nic.cz/turris/updater/updater/-/issues2020-10-08T23:34:37+02:00https://gitlab.nic.cz/turris/updater/updater/-/issues/253Pre-configured medkit generator2020-10-08T23:34:37+02:00Vojtech MyslivecPre-configured medkit generatorhttps://gitlab.nic.cz/turris/updater/updater/-/issues/223Print output from package's script not after they exited but at time of their...2019-05-06T17:47:30+02:00Karel KociPrint output from package's script not after they exited but at time of theirexecutionPrinting output only after they exited hides reason and informationwhere those scripts hanged.Printing output only after they exited hides reason and informationwhere those scripts hanged.https://gitlab.nic.cz/turris/updater/updater/-/issues/252Refactor URI2019-04-18T17:40:59+02:00Karel KociRefactor URIUpdater contains complicated uri handling and almost separate downloading framework (that is integrated with events). We should instead reimplement it from ground up in C (just as lua bindings) with dedicated downloading system. Idea is ...Updater contains complicated uri handling and almost separate downloading framework (that is integrated with events). We should instead reimplement it from ground up in C (just as lua bindings) with dedicated downloading system. Idea is to separate current downloader implementation from events and then use that to implement uri abstraction.
There should also be small feature that to simplify uri usage we should also accept strings without `URI://` format to be local paths (`file://` uri).
* [x] Separate downloader from events
* [x] Implement uri as a lua bindingsTurris OS 4.0