I'm debugging a package already in the Solus repository and I've been asked to apply a source change, rebuild and install.
However, I live by the teaching that nobody but eopkg touches /usr and I would rather patch the package instead.
The question is, how can I point solbuild to the local checkout with the changes?

  • davidjharder replied to this.

  • You can create a git patch of the change, but we don't currently have documentation for that. Honestly, I would recommend just following the Budgie instructions on Github. You can still revert after with sudo eopkg it --reinstall budgie-desktop, since that will reinstall Budgie from the Solus repo.

    I reported a bug in Budgie, and was asked to make a source code change, recompile and install (thus replacing the eopkg-installed budgie).
    I want instead to create a package with the patched budgie, which would be a local checkout in my HDD, install that and then, once testing is done, revert to budgie from the repo.
    However, I'm not sure what I can write in package.yml so that solbuild sees my local checkout.
    As far as I know, package.yml expects a link to a tarball...

    Though I suppose that if everything fails I can fork budgie to my github and get a tarball from there...

    You can create a git patch of the change, but we don't currently have documentation for that. Honestly, I would recommend just following the Budgie instructions on Github. You can still revert after with sudo eopkg it --reinstall budgie-desktop, since that will reinstall Budgie from the Solus repo.

    Thanks to both, I will try in the next days