# Cenralizing Control Over Polyrepo With Follows

**URL:** https://discourse.nixos.org/t/cenralizing-control-over-polyrepo-with-follows/67545
**Category:** Guides
**Created:** [August 3, 2025, 3:23pm UTC](https://discourse.nixos.org/t/cenralizing-control-over-polyrepo-with-follows/67545 "2025-08-03T15:23:51Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![psionik](https://discourse.nixos.org/user_avatar/discourse.nixos.org/psionik/32/3374_2.png) [@psionik](https://discourse.nixos.org/u/psionik)
#### Post date: [August 3, 2025, 3:23pm UTC](https://discourse.nixos.org/t/cenralizing-control-over-polyrepo-with-follows/67545/1 "2025-08-03T15:23:51Z")

</div>

> **[Positron - Only the Future Is Certain](https://positron.solutions/articles/centralizing-nix-dependencies)**
>
> Positron is connecting demand for downstream value
> creation with upstream enabling technologies. PrizeForge, our first product, is a
> production finance model for Open Source, ensuring that user communities can fund the
> ...

Described (with an example flake linked) is how to make poly repo always wind up with known sets of versions by defining concrete inputs in one central flake and using follows everywhere else.

I made some corrections. Latest update cycle made me aware of a few deprecated / non-recommended styles.

- No more `nix flake lock --update-input`
- Avoided the registry for naming the concrete central flake

The social metadata doesn’t match the link btw. This is a new site and I’m just doing everything as fast as I can.