Solus packaging for Python programs

JacekJagosz

palto42 You don't need to list all dependencies if one of your dependencies relies on other one. Because e.g. python-ruamel-yaml needs python3, you don't need to mention it again.
Normally you do that by doing eopkg info <dependency name> and look at dependencies (and sometimes dependencies of dependencies) and you don't need to include those. Also reverse dependencies are helpful, because they rely on that dependency.

palto42

I have managed to build borgmatic and all missing dependencies locally and the installation via eopkg worked 😀 . Thanks all for your support!

Now I have submitted a package request T9241 to add it to the Solus repository.

algent

palto42 can you share your package.yml for borgmatic? This is mine

palto42

algent This is mine, see some small differences:

You don't have the runtime dependency for ruamel.yaml (because pykwalify has it)
You added installations of the systemd and cron samples

https://gist.github.com/palto42/c4b2440ea8ae0bd8b037dc5d64fd4e58

algent

palto42 Are the builddeps: -pkgconfig(python3) -python-setuptools not required anymore for python packages?

pkconfig(python3) - not always, if it is needed, solbuild will complain for missing Python.h for example.
python-setuptools - is needed for python2 packages.

palto42 Is there a package naming convention to replace dots with hyphen? The original name of the ruamel packages uses dots like ruamel.yaml.clib and you replaced it with ruamel-yaml-clib.

I prefer using hyphen, and add python- to the python packages. No dots and underlines.

Different distros use different names for example.
Arch - python-ruamel.yaml.clib and python-ruamel-yaml
Fedora - python-ruamel-yaml-clib and python-ruamel-yaml

Check this links and you will get an idea.
python-ruamel.yaml.clib
python-ruamel-yaml-clib

davidjharder

@palto42 Thanks for taking a run at this. I just found out about Borgmatic and it looks promising

palto42

Updated my above package.yaml:

removed dependency python-ruamel.yaml (indirect dependency via pykwalify)
install README, CHANGELOG, cron example and systemd example to usr/share/doc/borgmatic

kyrios

palto42 install README, CHANGELOG, cron example and systemd example to usr/share/doc/borgmatic

Doesn't make sense to provide the cron example since Solus doesn't provide cron. Same for the changelog, it is useless to add it in the package. Since this info is available in the package history.

palto42

kyrios Agree that cron example is useless for Solus.
But how do I get the changelog of borgmatic into the package history? Currently it only shows "Packaging update" in my build.
One thing I noticed is that during make I get a warning WARN[17:39:08] Failed to obtain package git history error="No usable git history found". Currently this is just a local build project on my local git (Gitea), is this the reason why it ignores the git log?

kyrios

palto42 Because when a package is submitted for review, you have to provide a summary in the git message. This summary is usually a summarized changelog and this is what you see changelog tab of the packages in the software center.

palto42

kyrios Thanks for your help and patience!
Do I correctly assume that the package information is finally coming from the arc diff commit message (is remarkup format?) and not from my local git commit messages?
So I need to add changelog information in the arc diffcommit message, either by copy & paste from the program's changelog and/or by adding a link reference to the changelog (e.g. on source code page).

algent

palto42 No, you don't have to add changelog because this is a new package. Changelogs are required when you submit an update. Your case should be something similar to this package.

kyrios

palto42 Exactly 🙂