Search Criteria
Package Details: lqsd-bin 0.1.1-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/lqsd-bin.git (read-only, click to copy) |
---|---|
Package Base: | lqsd-bin |
Description: | LiQuid Screen Dim - Dim your screen smoothly. Precompiled binary version |
Upstream URL: | https://github.com/FunctionalHacker/lqsd |
Licenses: | MIT |
Conflicts: | lqsd |
Provides: | lqsd |
Submitter: | FunctionalHacker |
Maintainer: | FunctionalHacker |
Last Packager: | FunctionalHacker |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2020-01-19 23:08 (UTC) |
Last Updated: | 2022-06-12 09:18 (UTC) |
Latest Comments
FunctionalHacker commented on 2020-01-22 09:02 (UTC)
@yochananmarqos I ended up moving to GitHub as the place to store my binaries as Gitea doesn't seem to support it yet and GitLab has these idiotic random URLs.
Thanks again for your help.
yochananmarqos commented on 2020-01-20 21:31 (UTC) (edited on 2020-01-20 21:31 (UTC) by yochananmarqos)
I'm not really sure about from the GitLab end, but there's a couple ways to use releases in the PKGBUILD:
Source tarball:
Release tag:
FunctionalHacker commented on 2020-01-20 18:44 (UTC)
Alright I was not aware that this was the convention. The more you know. It's updated now.
Hey while I have you here, do you have any experience on distributing binaries from GitLab? The only way I found was attaching it to the release markdown and it gets assigned this random slug, which means I have to update the whole URL when I make a new release. Is there a better way to do it?
yochananmarqos commented on 2020-01-20 18:22 (UTC)
I meant actually install the LICENSE: ;)
FunctionalHacker commented on 2020-01-20 17:45 (UTC)
@yochananmarqos good catch. That's what you get for releasing software after midnight. I will update asap
yochananmarqos commented on 2020-01-20 01:34 (UTC)
You spelled license wrong and an MIT license should be included in the package.