Skip to content

TRE install friction: INSTALL.md and acro_init() tell different stories #52

@shamykyzer

Description

@shamykyzer

This came out of PR #49, related to automate updating changelog from PR names for ACRO-R, a bigger mismatch that failed macos-ci check constantly: the install guide tells the user to set up a Python environment by hand and install acro into it, but the R code in acro_init() also tries to do this automatically, the two paths do not check each other, so if a user already has acro available somewhere the code does not notice and still tries to install it from scratch, on a TRE that cannot reach PyPI this fresh install fails and the user is stuck, happy to be corrected if I am missing something

A few ideas worth gut checking me on,

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    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