*: replace nxt -> monogon
These are hopefully the last leftovers from the nxt monorepo.
This change breaks existing build containers and IntelliJ setups, and
unfortunately thrashes developer workstation Bazel caches.
Running `scripts/bin/destroy_container.sh &&
scripts/bin/create_container.sh` and then following the IntelliJ setup
guide in //README.md should be enough to fix everything.
Did that locally and was able to set up a fully working IntelliJ
IDE against this change.
Change-Id: I090f4e4f2ea03998569a4ea3d1aa4cd4ec570f8a
Reviewed-on: https://review.monogon.dev/c/monogon/+/61
Reviewed-by: Leopold Schabel <leo@nexantic.com>
diff --git a/build/fietsje/README.md b/build/fietsje/README.md
index ff990a3..723813f 100644
--- a/build/fietsje/README.md
+++ b/build/fietsje/README.md
@@ -6,9 +6,9 @@
Introduction
------------
-Fietsje is a dependency management system for Go dependencies in nxt. It does
-not replace either gomods or Gazelle, but instead builds upon both on them in
-a way that makes sense for our particular usecase: pulling in a large set of
+Fietsje is a dependency management system for Go dependencies in monogon. It
+does not replace either gomods or Gazelle, but instead builds upon both on them
+in a way that makes sense for our particular usecase: pulling in a large set of
dependency trees from third\_party projects, and sticking to those as much as
possible.
@@ -57,7 +57,7 @@
In general, `.collect()`/`.collectOverride()` calls should be limited only to
dependencies 'we' (as developers) want. These 'high-level' dependencies are
-large projects like Kubernetes, or direct imports from nxt itself. Every
+large projects like Kubernetes, or direct imports from monogon itself. Every
transitive dependency of those should just be enabled by calling `.use()`,
instead of another `.collectOverride()` call that might pin it to a wrong
version.
@@ -125,7 +125,7 @@
- if the dependency has little transitive dependencies, use `.inject()` to
add transitive dependencies manually after your `.collect()` call
- otherwise, extend fietsje to allow for out-of-tree go.mod/go.sum files kept
- within nxt, or come up with some other solution.
+ within monogon, or come up with some other solution.
Your new dependency might conflict with existing dependencies, which usually
manifests in build failures due to incompatible types. If this happens, you
diff --git a/build/fietsje/shelf.go b/build/fietsje/shelf.go
index ea709be..99a06c5 100644
--- a/build/fietsje/shelf.go
+++ b/build/fietsje/shelf.go
@@ -32,7 +32,7 @@
// The Shelf is a combined cache and dependency lockfile, not unlike go.sum. It's implemented as a text proto file on
// disk, and currently stores a single mapping of shelfKeys to shelfValues, which are in order a (importpath, version)
// tuple and the `locked` structure of a dependency.
-// The resulting shelf file should be commited to the nxt repository. It can be freely deleted to force recreation from
+// The resulting shelf file should be commited to the monogon repository. It can be freely deleted to force recreation from
// scratch, which can be useful as there is no garbage collection implemented for it.
// The 'lockfile' aspect of the Shelf is counter-intuitive to what readers might be used to from other dependency
// management systems. It does not lock a third-party dependency to a particular version, but only locks a well defined