|
@@ -45,7 +45,7 @@ Package Specific Resources:
|
|
|
|
|
|
|
|
3. Manifest:
|
|
3. Manifest:
|
|
|
- Include ALL required fields
|
|
- Include ALL required fields
|
|
|
- - Set `simpleBuildEnvironment` flag for LFS packages
|
|
|
|
|
|
|
+ - Set `simpleBuildEnvironment` flag for script simplicity
|
|
|
- Point `md` property to `PACKAGE.md`
|
|
- Point `md` property to `PACKAGE.md`
|
|
|
- Leave `provides` section empty
|
|
- Leave `provides` section empty
|
|
|
|
|
|
|
@@ -55,22 +55,25 @@ Package Specific Resources:
|
|
|
- If there is a missing build dependency stop and notify the user (by asking a question)
|
|
- If there is a missing build dependency stop and notify the user (by asking a question)
|
|
|
- Add any such dependencies `depends` section of the manifest.
|
|
- Add any such dependencies `depends` section of the manifest.
|
|
|
|
|
|
|
|
-**VALIDATION:**
|
|
|
|
|
|
|
+**METHOD:**
|
|
|
|
|
|
|
|
-1. Create complete package structure
|
|
|
|
|
|
|
+1. Create folder structure, `MANIFEST.usm`, and an `acquire.sh` script
|
|
|
2. Execute `usm manifest acquire` in package directory
|
|
2. Execute `usm manifest acquire` in package directory
|
|
|
-3. Fix any errors, investigating extracted source for possible documentation in files like `INSTALL` or `README`
|
|
|
|
|
-4. Execute `usm manifest autoprovides --replace --debug` in package directory
|
|
|
|
|
-5. Verify `provides` was populated correctly. Missing entries indicate a problem with the `install` script.
|
|
|
|
|
-6. Fix any errors
|
|
|
|
|
-7. Verify compliance with Astrologue standards
|
|
|
|
|
|
|
+3. Fix any errors with the acquire script
|
|
|
|
|
+4. Look in the extracted source archive for installation documentation in a file like `INSTALL` or `README`
|
|
|
|
|
+5. Update the `licences` section in `MANIFEST.usm` to point to the `text` files of the licences in the extracted archive.
|
|
|
|
|
+6. Create other required and optional scripts, and update `MANIFEST.usm`.
|
|
|
|
|
+7. Execute `usm manifest autoprovides --replace --debug` in package directory
|
|
|
|
|
+8. Verify `provides` was populated correctly. Missing entries indicate a problem with the `install` script.
|
|
|
|
|
+9. Fix any errors
|
|
|
|
|
+10. Write a friendly `PACKAGE.md`
|
|
|
|
|
+11. Verify compliance with Astrologue standards
|
|
|
|
|
|
|
|
**PACKAGE SPECIFICATION:**
|
|
**PACKAGE SPECIFICATION:**
|
|
|
|
|
|
|
|
**Name:** (package name)
|
|
**Name:** (package name)
|
|
|
**Version:** (package version)
|
|
**Version:** (package version)
|
|
|
**Homepage URL:** (url)
|
|
**Homepage URL:** (url)
|
|
|
-**Homepage URL:** (url)
|
|
|
|
|
-**Homepage URL:** (url)
|
|
|
|
|
|
|
+**Source Archive URL:** (url)
|
|
|
|
|
|
|
|
Create a production-ready package following all requirements precisely.
|
|
Create a production-ready package following all requirements precisely.
|