summaryrefslogtreecommitdiff
path: root/app-admin/scout/files/scout-0.5.0-hedronfire-examples.patch
blob: 2fcae412ff1626643a251a638610a6c65d03a1cd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
--- a/README.md
+++ b/README.md
@@ -2,18 +2,18 @@
 ==============
 
 Scout manages repositories and the installed system's profile. Install
-`app-admin/scout`; version 0.4.0 owns the complete client runtime and both the
+`app-admin/scout`; version 0.5.0 owns the complete client runtime and both the
 `scout` and compatibility `aerie` commands. It requires neither the Aerie package
-nor the Foundry/Crucible server runtime. `app-admin/aerie` 0.4.0 is a compatibility
+nor the Foundry/Crucible server runtime. `app-admin/aerie` 0.5.0 is a compatibility
 package depending on Scout, so existing package selections work.
 
 ```sh
 scout
-scout init https://www.srcux.com/git/srcux.git --release develop
+scout init https://git.hedronfire.com/hedronfire.git --release develop
 scout sync
-scout create personal --parent srcux
+scout create personal --parent hedronfire
 scout repo list
-scout repo show srcux
+scout repo show hedronfire
 scout profile list
 scout profile check
 scout profile gui sway
@@ -25,7 +25,7 @@
 
 On an unconfigured machine, plain `scout` in a terminal asks for the repository
 URL, checks its published branches, and asks which release to use. It suggests
-the Srcux URL and the remote's default branch. Review the name,
+the Hedronfire URL and the remote's default branch. Review the name,
 release, and checkout path, then save. Existing configured machines show their
 main repository and release instead. Help and noninteractive commands never
 start a wizard.
@@ -44,8 +44,8 @@
 
 ```sh
 scout --config /path/scout.yml --repos-conf /path/repos.conf --json init \
-  https://www.srcux.com/git/srcux.git \
-  --name srcux --release develop --location /path/checkout
+  https://git.hedronfire.com/hedronfire.git \
+  --name hedronfire --release develop --location /path/checkout
 ```
 
 Setup refuses existing configurations, conflicting registrations, and occupied
@@ -168,22 +168,22 @@
 PYTHONPATH=src python3 -m aerie --help
 ```
 
-Srcux migration
----------------
+Distribution migration
+----------------------
 
 Installing Scout alone does not change the active repository or profile.
-Once the Srcux service is published, migrate an existing downloaded client tree
-between package operations:
-
-```sh
-scout migrate srcux --check
-scout migrate srcux
+With Scout 0.5.0 installed, migrate an existing downloaded Srcux or BaldEagleOS
+client tree between package operations:
+
+```sh
+scout migrate hedronfire --url https://git.hedronfire.com/hedronfire.git --check
+scout migrate hedronfire --url https://git.hedronfire.com/hedronfire.git
 scout profile
 scout repo list
 scout sync
 ```
 
-The check prepares a separate checkout at `/var/db/repos/srcux`, verifies that
+The check prepares a separate checkout at `/var/db/repos/hedronfire`, verifies that
 the old Git commit is in its ancestry, and checks every mapped profile parent.
 The second command switches the registration and profile, preserving selections
 and local parent lines. It also removes `-repo` from disabled local overlays
@@ -199,7 +199,7 @@
 targets. `--url URL` and `--location PATH` are available for an alternate endpoint
 or new checkout location.
 
-A private recovery record at `/var/lib/scout/migrations/srcux/migration.json`
+A private recovery record at `/var/lib/scout/migrations/hedronfire/migration.json`
 retains original file contents. Repeat the same command after interruption;
 recovery refuses to overwrite intervening operator edits. Keep that record and
 the old checkout until the migration is accepted. The compatibility `aerie`
@@ -207,5 +207,10 @@
 
 Profile-aware repositories may declare `schema_version = 1` and a relative
 `profile_prefix` in `profiles/scout.json`. Repositories without that descriptor
-keep the legacy profile namespace. The Srcux migration also requires a matching
+keep the legacy profile namespace. A distribution migration also requires a matching
 entry in `previous_identities` with `repository` and `profile_prefix` fields.
+
+`scout migrate NAME --url URL` supports other repository identities. The original
+`scout migrate srcux` command and its recovery records remain supported, using
+the legacy Srcux URL. Hedronfire currently publishes `develop`; migration does
+not change a client's selected release to bypass a missing branch.
--- a/etc/scout.yml.example
+++ b/etc/scout.yml.example
@@ -1,3 +1,3 @@
 global:
     release: develop
-    reposconfpath: /etc/portage/repos.conf/srcux.conf
+    reposconfpath: /etc/portage/repos.conf/hedronfire.conf