- One file to rule them all
- Simple to follow instruction (so terminal beginner can follow them)
- You should be able to package something by just scrolling down
- Separate beginner and advance usage
- Generall Information which arent crutial to packaging can be in a separate file
- Having just once example not multible to less confuse stuff
- Agrement to similar word usage (exampl. diff/patch)
- structure of the file(s) okay?
- missing stuff?
- solbuild
- abi-wizard
- common
- phabricator
- Repo
- Diff
- Maintainer
- IRC: Solus-Dev
- Setting up Packager file
- Switch to the unstable repo
- Setting up solbuild
- update solbuild
- delete solbuild cache/all cache
- Setting up common
- update common file
- setting up Archanist
- Setting up a local repo
- Setting up a custom repo
- manuall indexing
- creating custom profiles
- How is a Package.yml is set up (link to another file?)
- Generating a Package.yml
- Which information have to be provided (lisense, infos etc.)
- How to search for builddeps/rundeps
- different Macros (link to another file?)
- How to build your package
- Bumping a Package
- How to check your .eopkg file for issues
- Maintainer file creating
- installing extra files from source
- creating own extra files
- tmp files
- Patterns
- Replace/rename
- optimize values
- How to use a patch
- command %patch
- command %apply_patches
- Security Patch
- How to add an upstream patch
- command wget
- How to create your own patch from code
- Update alias
- respect the Maintainer file
- What needs to be done before submitting (Checks)
- version/release
- abi changes
- path changes
- Check if on the correct commit
- Creating the diff
- Submitting for Review
- Correct Changelog
- Test plan (not only Unit tests)
- Submitting stacks
- Updating Task Information
- what to do reg the changes
- how to recreate the diff
- squashing commits