Switch all references to github.com/containers/libpod -> podman

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

1 files changed, 21 insertions, 21 deletions

diff --git a/dependencies/analyses/README.md b/dependencies/analyses/README.md
index 734058045..7309b1fa8 100644
--- a/dependencies/analyses/README.md
+++ b/dependencies/analyses/README.md
@@ -20,16 +20,16 @@ WORK=/tmp/go-build794287815
 
 # 2) Set the work directory as an environment variable and call the analysis script
 [libpod]$ WORK=/tmp/go-build794287815 ./dependencies/analyses/go-archive-analysis.sh | head -n10
-17M github.com/containers/libpod/cmd/podman/cliconfig
-13M github.com/containers/libpod/vendor/github.com/DataDog/zstd
-10M github.com/containers/libpod/vendor/k8s.io/api/core/v1
+17M github.com/containers/podman/cmd/podman/cliconfig
+13M github.com/containers/podman/vendor/github.com/DataDog/zstd
+10M github.com/containers/podman/vendor/k8s.io/api/core/v1
 3.7M net/http
-3.7M github.com/containers/libpod/libpod
+3.7M github.com/containers/podman/libpod
 3.2M runtime
-2.7M github.com/containers/libpod/vendor/github.com/gogo/protobuf/proto
-2.5M github.com/containers/libpod/vendor/k8s.io/apimachinery/pkg/apis/meta/v1
-2.3M github.com/containers/libpod/vendor/github.com/vishvananda/netlink
-2.1M github.com/containers/libpod/cmd/podman/varlink
+2.7M github.com/containers/podman/vendor/github.com/gogo/protobuf/proto
+2.5M github.com/containers/podman/vendor/k8s.io/apimachinery/pkg/apis/meta/v1
+2.3M github.com/containers/podman/vendor/github.com/vishvananda/netlink
+2.1M github.com/containers/podman/cmd/podman/varlink
 ```
 
 The output of the `go-archive-analysis.sh` script is a sorted table with the size in bytes followed by the package.
@@ -51,16 +51,16 @@ Running such an analysis on libpod may look as follows:
 
 # 2) Run the script with the binary as an argument
 [libpod]$ ./dependencies/analyses/nm-symbols-analysis.sh ./bin/podman | grep "containers/libpod/libpod" | head -n10
-299             github.com/containers/libpod/libpod.(*BoltState).AddContainer
-658             github.com/containers/libpod/libpod.(*BoltState).AddContainerToPod
-2120            github.com/containers/libpod/libpod.(*BoltState).AddPod
-3773            github.com/containers/libpod/libpod.(*BoltState).AddPod.func1
-965             github.com/containers/libpod/libpod.(*BoltState).AddVolume
-1651            github.com/containers/libpod/libpod.(*BoltState).AddVolume.func1
-558             github.com/containers/libpod/libpod.(*BoltState).AllContainers
-282             github.com/containers/libpod/libpod.(*BoltState).AllContainers.func1
-1121            github.com/containers/libpod/libpod.(*BoltState).AllContainers.func1.1
-558             github.com/containers/libpod/libpod.(*BoltState).AllPods
+299             github.com/containers/podman/libpod.(*BoltState).AddContainer
+658             github.com/containers/podman/libpod.(*BoltState).AddContainerToPod
+2120            github.com/containers/podman/libpod.(*BoltState).AddPod
+3773            github.com/containers/podman/libpod.(*BoltState).AddPod.func1
+965             github.com/containers/podman/libpod.(*BoltState).AddVolume
+1651            github.com/containers/podman/libpod.(*BoltState).AddVolume.func1
+558             github.com/containers/podman/libpod.(*BoltState).AllContainers
+282             github.com/containers/podman/libpod.(*BoltState).AllContainers.func1
+1121            github.com/containers/podman/libpod.(*BoltState).AllContainers.func1.1
+558             github.com/containers/podman/libpod.(*BoltState).AllPods
 ```
 
 Running the script can help identify sources of bloat and reveal potential candidates (e.g., entire packages, types, or function) for refactoring.
@@ -80,9 +80,9 @@ Running such a dependency-tree analysis may look as follows:
 
 
 ```
-[libpod]$ ./dependencies/analyses/dependency-tree.sh github.com/containers/libpod
-[libpod]$ grep "^github.com/containers/libpod/pkg/registries" direct-tree.txt
-github.com/containers/libpod/pkg/registries: github.com/containers/libpod/vendor/github.com/containers/image/pkg/sysregistriesv2, github.com/containers/libpod/vendor/github.com/containers/image/types, github.com/containers/libpod/pkg/rootless, github.com/containers/libpod/vendor/github.com/docker/distribution/reference, github.com/containers/libpod/vendor/github.com/pkg/errors, os, path/filepath, strings
+[libpod]$ ./dependencies/analyses/dependency-tree.sh github.com/containers/podman
+[libpod]$ grep "^github.com/containers/podman/pkg/registries" direct-tree.txt
+github.com/containers/podman/pkg/registries: github.com/containers/podman/vendor/github.com/containers/image/pkg/sysregistriesv2, github.com/containers/podman/vendor/github.com/containers/image/types, github.com/containers/podman/pkg/rootless, github.com/containers/podman/vendor/github.com/docker/distribution/reference, github.com/containers/podman/vendor/github.com/pkg/errors, os, path/filepath, strings
 ```
 
 As shown above, the script's output can then be used to query for specific packages (e.g, with `grep`).