3 ms·

I presume you mean lightsd. Nifty stuff. What do you think of Suse's OBS? I believe you're squarely in its target audience. And hats off to you for going th

by keenerd 10y ago

I presume you mean lightsd. Nifty stuff. What do you think of Suse's OBS? I believe you're squarely in its target audience. And hats off to you for going the extra mile for your project! Your PKGBUILD even looks quite good. Would you like some assistance in writing a -git pkgbuild for people who want to try the absolute newest commit?

kalessin 10y ago
Thank you! Yes, I was referring to my work on lightsd. I didn't know about Suse's OBS until this thread, I guess I need to look into it. I have been building my own CI/CD pipeline on top of Buildbot so far. It's a PITA, but leaves a lot of room for creativity, hopefully it will be rewarding down the road. I don't know about the -git thing for PKGBUILD, what's the syntax/documentation?
- keenerd 10y ago
  It is briefly mentioned in the manpage, https://www.archlinux.org/pacman/PKGBUILD.5.html https://www.archlinux.org/pacman/PKGBUILD.5.html, but basically a pkgbuild can use a git repo as a source directly. Here's an example: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pacman-git https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pacma... Compare it to pacman's release-based pkgbuild: https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/pacman https://git.archlinux.org/svntogit/packages.git/tree/trunk/P... The major differences are the "git" url in the sources, the provides/conflicts metadata and the dynamic pkgver() function.
  - kalessin 10y ago
    Nice, maybe I'll consider this for dogfooding, thank you for the explanations!
- cyphar 10y ago
  SUSE's OBS is in my biased opinion (I work at SUSE), probably one of the better ways of solving this problem for ISVs. You don't need a build infrastructure, you can get feedback from distribution maintainers and submission to the main distribution is surprisingly painless. Actually you can build packages for non-SUSE distributions on OBS as well, so it's even more versatile than just the openSUSE community's distributions.

by keenerd 10y ago

kalessin 10y ago

Thank you! Yes, I was referring to my work on lightsd. I didn't know about Suse's OBS until this thread, I guess I need to look into it. I have been building my own CI/CD pipeline on top of Buildbot so far. It's a PITA, but leaves a lot of room for creativity, hopefully it will be rewarding down the road. I don't know about the -git thing for PKGBUILD, what's the syntax/documentation?

keenerd 10y ago
It is briefly mentioned in the manpage, https://www.archlinux.org/pacman/PKGBUILD.5.html https://www.archlinux.org/pacman/PKGBUILD.5.html, but basically a pkgbuild can use a git repo as a source directly. Here's an example: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pacman-git https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=pacma... Compare it to pacman's release-based pkgbuild: https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/pacman https://git.archlinux.org/svntogit/packages.git/tree/trunk/P... The major differences are the "git" url in the sources, the provides/conflicts metadata and the dynamic pkgver() function.
- kalessin 10y ago
  Nice, maybe I'll consider this for dogfooding, thank you for the explanations!
cyphar 10y ago
SUSE's OBS is in my biased opinion (I work at SUSE), probably one of the better ways of solving this problem for ISVs. You don't need a build infrastructure, you can get feedback from distribution maintainers and submission to the main distribution is surprisingly painless. Actually you can build packages for non-SUSE distributions on OBS as well, so it's even more versatile than just the openSUSE community's distributions.