소스 검색

docs(manifest): clarify resource reference format in dependencies

Update dependency management and resource types documentation to emphasize
that resource references must specify actual filesystem files, not package
names. Added clear examples showing correct usage like `bin:find` instead
of `bin:findutils` and `bin:ls` instead of `bin:coreutils`. This clarifies
how the manifest system resolves dependencies by checking for file
existence in system directories.
clanker 1 개월 전
부모
커밋
4ad14c7b22
2개의 변경된 파일16개의 추가작업 그리고 4개의 파일을 삭제
  1. 10 3
      slopdocs/structure.usm.manifest.dependency-management.md
  2. 6 1
      slopdocs/structure.usm.manifest.resource-types.md

+ 10 - 3
slopdocs/structure.usm.manifest.dependency-management.md

@@ -45,8 +45,8 @@ Resources required to run management scripts (build, install, remove).
 ```json
 "manage": [
   "bin:bash",
-  "bin:coreutils",
-  "bin:findutils"
+  "bin:ls",
+  "bin:find"
 ]
 ```
 
@@ -68,7 +68,14 @@ Resources required to download and extract source code.
 
 ## Resource Reference Format
 
-All dependencies use the format `[resource-type]:[resource-name]`:
+All dependencies use the format `[resource-type]:[resource-name]` where the resource name refers to an actual installed file on the filesystem, NOT a package name.
+
+**Important**: Dependencies must reference specific files, not package names. For example:
+- Use `bin:find` to reference the find utility executable, NOT `bin:findutils`
+- Use `bin:ls` to reference the ls executable, NOT `bin:coreutils`
+- Use `lib:libssl.so` to reference the SSL library, NOT `bin:openssl`
+
+Resource references are resolved by checking for the existence of the specified file in the appropriate system directories.
 
 ### Common Runtime Dependencies
 ```json

+ 6 - 1
slopdocs/structure.usm.manifest.resource-types.md

@@ -107,7 +107,12 @@ Example: `tag:category.subcategory.feature`
 
 ## Resource Reference Format
 
-Resource references follow the pattern: `type:name`
+Resource references follow the pattern: `type:name` where the name refers to an actual installed file on the filesystem, NOT a package name.
+
+**Important**: Resource references must specify actual files, not package names. For example:
+- Use `bin:find` to reference the find utility executable, NOT `bin:findutils`
+- Use `bin:ls` to reference the ls executable, NOT `bin:coreutils`
+- Use `lib:libssl.so` to reference the SSL library, NOT `bin:openssl`
 
 Examples:
 - `bin:ls` - The ls executable