Skip to content

The biggest problem for reproducible builds: MOKO Resources. #73

@nubesurrealista

Description

@nubesurrealista

I'm trying to get Kumo accepted into IzzyOnDroid, but we've hit a snag: reproducible builds. Even though we've taken steps to cut down on these kinds of issues and make it more deterministic, we still have a major enemy: MOKO Resources. I honestly don't really know how to pull this off because MOKO seems completely dynamic with no way to make it more static, I'm even considering exploring the possibility of dropping it entirely, but that would probably be a ton of work, idk, if anyone has experience with MOKO and reproducible builds, I'll take any help I can get.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions