Make secondary manifest location more specific

This commit is contained in:
mtkennerly 2023-03-27 10:50:09 +08:00
parent b7c9cd66f8
commit 70f541fc26
No known key found for this signature in database
GPG key ID: E764BE00BE6E6408

View file

@ -92,8 +92,8 @@ Tools must implement the following in addition to respecting the schema:
This is important for secondary manifests to work correctly without
hard-coding their location.
* If a tool supports secondary manifests, they must be automatically detected
when they are named `.ludusavi.yaml` and exist anywhere within a configured
root.
when they are named `.ludusavi.yaml` and located directly in `<base>`.
For example, a Steam game's secondary manifest would be `<root>/steamapps/common/<game>/.ludusavi.yaml`.
Tools may also: