Skip to content

what to do with packages that are also in nixpkgs? #642

@bbjubjub2494

Description

@bbjubjub2494

Context

The script attacked indicates that the following packages in are also in nixpkgs:

  • besu
  • blst
  • eigenlayer
  • erigon
  • foundry
  • geth (false negative since it's called go-ethereum)
  • heimdall false positive due to a namesake
  • lighthouse
  • mev-boost
  • reth

list_nixpkgs_packages.py

Description

Are there benefits to having these derivations duplicated here? If not we would be better served by replacing them with aliases to nixpkgs-unstable (along with an automated flake update flow)

Before submitting

  • I have verified that my idea is a change request and not a bug report

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions