Conor425/ludusavi-manifest
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Make secondary manifest location more specific

Browse source
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
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
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 This is important for secondary manifests to work correctly without
hard-coding their location. hard-coding their location.
* If a tool supports secondary manifests, they must be automatically detected * If a tool supports secondary manifests, they must be automatically detected
when they are named `.ludusavi.yaml` and exist anywhere within a configured when they are named `.ludusavi.yaml` and located directly in `<base>`.
root. For example, a Steam game's secondary manifest would be `<root>/steamapps/common/<game>/.ludusavi.yaml`.
Tools may also: Tools may also: