Packages missing the homepage key

[davidjharder]

Many Solus packages do not have a homepage key set in package.yml. See the full list yourself by installing the ripgrep package and running the following ripgrep (rg) command from the root of this repository:

rg --files-without-match "homepage" -g '*package.yml' | sort

Guidance on fixing

• Refer to our help site if you are new to packaging and need to set up your system: https://help.getsol.us/docs/packaging/prepare-for-packaging
• If a package doesn't have a homepage, use a portion of the source URL.
  • Example: The package zimg does not seem to have a dedicated homepage, so you would use https://github.com/sekrit-twc/zimg
• homepage goes after source, see https://help.getsol.us/docs/packaging/package.yml. Some existing package.ymls will have homepage in other places; don't worry about that
• After you have added a homepage, rebuild the package. This checks that the homepage was added correctly.
• One Pull Request for each package
• If you would like to fix many packages you can pick a letter and fix packages starting with that letter
• For programming language modules (perl, python, etc), a webpage is preferred (e.g. https://metacpan.org/pod/Acme or https://pypi.org/project/sync/). If there is no webpage at all for the module, provide the most relevant information possible.

The List

• 2300 1875 1742 1339 1101 989 829 650 606 511 435 319 307 301 207 76 50 1 items
• drive 🗑️ drive: deprecate #4200
• glog glog: Fix build & housekeeping #4448
• jabref Jabref: Update to 5.15 along with packaging fixes #3605
• libgltf 🗑️ libgltf #3792
• libgnomecanvas2 🗑️libgnomecanvas2 #3793
• liburing liburing: Update to 2.7 #3826
• lyrebird 🗑️ lyrebird: Deprecate #4209
• modelio ❌ modelio does not build #2604 🗑️ Deprecate modelio #4701
• opencollada 🗑️remove opencollada from blender #3708 then deprecate OpenCOLLADA #2738
• pandoc-include-code pandoc-include-code does not build #3854
• pcsxr 🗑️pcsxr #3856
• piksemel ⛔ Staff only please piksemel: Housekeeping #4700
• pspp pspp: Update to v2.0.1 #4333
• python ⛔ Staff only please python: does not build #4679
• python-zope.hookable python-zope.hookable: Update to v7.0 #4187
• qt6-gamepad ❌ qt6-gamepad: does not build #4189 Nothing used it 🗑️ qt6-gamepad: deprecate #4218
• rawstudio rawstudio: Update to latest git #4284
• redis 🗑️ valkey: add at 8.0.1 #3926
• retroshare retroshare: Update to v0.6.7.2 #4212
• rxvt-unicode rxvt-unicode: Add homepage #4253
• syslinux❌ syslinux does not build #3012 syslinux: Update to v6.04 and housekeeping #4702
• xsd xsd: Fix build and housekeeping #4346

[Achilleshiel]

For now I have 2 follow up questions.

1. Do you really want to have 2300 PR?
2. If packages do not have a homepage but they do have a mention on the cpan or pypi network. Should that count as a homepage?

[TraceyC77]

1. 2300 pull requests would be a good problem to have, in that we would have most or all of our packages updated. We don't expect to get that many at once, this will likely be a long term effort
2. Good questions. Yes, language related packages that do not have a website can have a link to their package. If there is a webpage of some sort, we prefer that. For instance, perl modules can be found on metacpan.org. I'll update in the issue description

[malfisya]

After you have added a homepage, rebuild the package. This checks that the homepage was added correctly.

Is this enough? Or do i have to have test plan too? If so, I don't know how to test a library (eg: zziplib). I'm planning to help out with this, starting from letter "z". (I'm total newbie). Thank you

[TraceyC77]

After you have added a homepage, rebuild the package. This checks that the homepage was added correctly.

Is this enough? Or do i have to have test plan too? If so, I don't know how to test a library (eg: zziplib). I'm planning to help out with this, starting from letter "z". (I'm total newbie). Thank you

Thanks for helping us with these homepages.

I would say the test plan can just be something like "verified the added homepage loads information about the package". You don't need to test the library or package itself, since you're not changing anything but the homepage information. This doesn't change how the software behaves.

Let us know if you have any other questions.