WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Consider adding Weave as an additional recipe output #167

@flferretti

Description

@flferretti

Comment:

weave has become increasingly important for workflows that rely on wandb. There is an existing weave-feedstock, but it appears to be abandoned and cannot be adopted or superseded due to conda-forge policies on feedstock ownership and replacement. Because of this, updating or reviving the standalone weave-feedstock is not feasible.

To ensure that users can obtain an up-to-date version of Weave through conda-forge, I propose to add a wandb-weave subpackage to the existing wandb-feedstock.
The subpackage would be distributed alongside wandb, following conda-forge’s multi-output recipe patterns. This avoids conflicts with the abandoned weave-feedstock while still providing a supported path for conda-forge users to install Weave.

I'd like to hear from the @conda-forge/wandb whether this approach would be acceptable, and if so, I’m happy to contribute with a PR

FYI @giotherobot

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions