Initial commit of QMMP
No Linters Available
No Unit Test Coverage
A TEST PLAN is a little verification that the package is correct and functioning. Example: You build a pdf reader that it's inclusion was ACCEPTED, packaged it, tested locally and then You write in the TEST PLAN something like: "Opened a pdf and saw its contents".
In your current case you might need to put: "Played some audio tracks successfully".
@melosaiyan I've forgot to mention something important: When You upload a diff that solves a package request You need to mention in the summary that the inclusion of the package fixes it. E.g.:
Initial commit of tarantula The inclusion of tarantula fixes TXXXX Signed-off-by: Your Name <firstname.lastname@example.org>
In your case it would be:
Initial Commit of QMMP The inclusion of qmmp fixes T5356 Signed-off-by: Brian Urbina <email@example.com>
P.S.: You have to make some modifications in your package.yml.
Should be GPL-2.0-or-later.
The order of the dependencies should be in alphabetical order like this:
- pkgconfig(libexample) - pkgconfig32(libexample) - example-tools
Search for package duplicates like pkgconfig(flac) pkgconfig(flac++)
Also the indentation is not 8 spaces, it's 4 spaces
@melosaiyan The correct place to mention that it "Fixes TNNN" is in the summary. You don't need to have it in the commit message.
Please make sure that you aren't listing any pkgconfigs that are dependencies of the ones already listed.
You changed it in the pacakge.yml, but a rebuild is needed to fix it in the pspec.