Several of the project's Cargo.toml files contained [package.metadata.deb] sections that described how to create a deb package with cargo-deb. These packages were all given the Fastly-specific fst- prefix for their package name and installation path (e.g. /opt/fst-lucetc/...). We do not use them inside Fastly anymore, and I'm not aware of any external users who depend on them either.
Several of the project's
Cargo.tomlfiles contained[package.metadata.deb]sections that described how to create a deb package withcargo-deb. These packages were all given the Fastly-specificfst-prefix for their package name and installation path (e.g./opt/fst-lucetc/...). We do not use them inside Fastly anymore, and I'm not aware of any external users who depend on them either.