[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 68851e2: Document commands for updating propr

From: Greg Chicares
Subject: [lmi-commits] [lmi] master 68851e2: Document commands for updating proprietary repository
Date: Wed, 3 Nov 2021 10:04:53 -0400 (EDT)

branch: master
commit 68851e2211bcb819e5231f821f17dfb25da2b80f
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Document commands for updating proprietary repository
    Explained how to use the technique discussed here:
    to maintain an up-to-date bare repository of proprietary information
    outside any chroot on a corporate server.
 gwc/redhat_rebuild.sh | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/gwc/redhat_rebuild.sh b/gwc/redhat_rebuild.sh
index ecd405d..80e9a8f 100755
--- a/gwc/redhat_rebuild.sh
+++ b/gwc/redhat_rebuild.sh
@@ -2,6 +2,18 @@
 set -evx
+# Before running this script, ensure that the proprietary repository
+# maintained outside any chroot is up to date. For example, if:
+#  - chroot 'lmi_bullseye_3' has a current proprietary repository;
+#  - '/srv/cache_for_lmi/blessed/proprietary' is out of date; and
+#  - a new chroot is to be created;
+# then run these commands:
+#   pushd /srv/cache_for_lmi/blessed/proprietary
+#   git fetch /srv/chroot/lmi_bullseye_3/opt/lmi/blessed/proprietary 
+# If, in the current chroot ('lmi_bullseye_3' in the example above),
+# the "blessed" repository is significantly behind the current working
+# copy, then first of all log into that chroot and do 'git push'.
             echo 'check_certificate = off' >> ~/.wgetrc
 sudo sh -c "echo 'check_certificate = off' >> ~/.wgetrc"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]