Skip to content

Why are we even extracting the compiler to the user's filesystem? #25

@Phantomical

Description

@Phantomical

This is more a note for myself to investigate later. There's been a number of user reports where unzipping the burst compiler fails for whatever reason. After thinking about this for a bit I'm not entirely sure that we should even be extracting the compiler at all. CKAN can already extract a zip for us, so if we have CKAN unpack the compiler package under 000_KSPBurst/Compiler we could avoid needing to do any unzipping at all.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions