Search Criteria
Package Details: i3lock-color-git r506.5bbdd02-1
| Git Clone URL: | https://aur.archlinux.org/i3lock-color-git.git (read-only) |
|---|---|
| Package Base: | i3lock-color-git |
| Description: | An improved screenlocker based upon XCB and PAM with color configuration support |
| Upstream URL: | https://github.com/PandorasFox/i3lock-color |
| Keywords: | i3 i3lock i3wm lock security x11 xorg |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | brandon099 |
| Maintainer: | brandon099 |
| Last Packager: | brandon099 |
| Votes: | 29 |
| Popularity: | 0.257754 |
| First Submitted: | 2015-08-13 22:44 |
| Last Updated: | 2018-08-13 22:01 |
Dependencies (8)
- cairo (cairo-git, cairo-dfb, cairo-minimal, cairo-infinality, cairo-nomesa, cairo-ubuntu, cairo-infinality-ultimate)
- libev (milter-manager-git)
- libjpeg-turbo (mozjpeg-git, mozjpeg)
- libxkbcommon-x11 (libxkbcommon-git)
- pam (pam-selinux)
- xcb-util-image
- xcb-util-xrm (xcb-util-xrm-git)
- git (git-git) (make)
Required by (17)
- betterlockscreen (requires i3lock-color)
- betterlockscreen-git (requires i3lock-color)
- i3-gaps-doubleborder (requires i3lock) (optional)
- i3-gaps-next-git (requires i3lock) (optional)
- i3-git (requires i3lock) (optional)
- i3-kde (requires i3lock) (optional)
- i3-wm-iconpatch (requires i3lock) (optional)
- i3lock-fancy-dualmonitors-git (requires i3lock)
- i3lock-fancy-git (requires i3lock)
- i3lock-fancy-multimonitor-git (requires i3lock)
- i3lock-next-git (requires i3lock-color)
- i3lock-wrapper (requires i3lock)
- i3lockmore-git (requires i3lock)
- lockd (requires i3lock)
- lockd-git (requires i3lock) (optional)
- oblogout-blurlock (requires i3lock)
- qtshutdownmenu-git (requires i3lock)
Latest Comments
1 2 3 4 Next › Last »
brandon099 commented on 2018-08-13 22:02
Removed hard-coded -j8 and added the new xcb-xrm dependency.
jaantoots commented on 2018-07-08 15:06
Please remove "-j8" from make. This should be configured in the MAKEFLAGS variable in makepkg.conf as a system-wide option.
S13ntist commented on 2018-07-07 11:34
Missing dependency on xcb-util-xrm
Fails to build in clean chroot:
configure: error: Package requirements (xcb-xrm) were not met: Package 'xcb-xrm', required by 'virtual:world', not found
brandon099 commented on 2017-12-08 00:41
@Pandoras_Fox, thanks for the gist with most of the changes needed to support your changes in the Github repo. I made a few additional tweaks, and we should be all up-to-date now.
Pandoras_Fox commented on 2017-12-06 17:35
https://gist.github.com/pandorasfox/aa9a98b607a13c765bfd90126254e490
I figured that as long as the pkgbuild was changing, this was probably as good a time as any to get around to updating my github username.
Pandoras_Fox commented on 2017-12-06 03:27
actually, I think that you could do something like:
git tag aur_build && autoreconf -fi && ...
Feel free to make an issue on github or whatever if there's something I can do to make it easier.
Pandoras_Fox commented on 2017-12-06 03:20
This PKGBUILD is very likely to break when I update the package later today or tomorrow to match upstream (upstream moved to using gnu autotools, which has been kinda weird, but a bit useful for the address sanitization stuff).
I'm looking into forcing a way for the build process to not do a debug build if it's done from git. Currently, you'll want to do something like:
autoreconf -fi && ./configure && cd x86_64-pc-linux-gnu && make -j8
or something. There'll probably be an option for the ./configure or something, though.
brandon099 commented on 2017-10-01 23:52
@ibrokemypie: Just added i3lock-color to the provides. Thanks!
ibrokemypie commented on 2017-09-29 12:22
Hey, would you be able to add i3lock-color to the provides?
I have put together packages for i3lock-color (the non-git version) and i3lock-next which requires i3lock-color (git or otherwise), something which cannot be fulfilled by other i3lock packages.
Thanks!
Pandoras_Fox commented on 2017-09-13 18:07
Looks like the SSE stuff used for blurring is a large part of it; dunno when I'll be able to get around to working out what to do. I don't really want to cut out a whole bunch of that to get it to work, since it'll make maintaining it pretty hard.
I might see if I can do some stuff with compile flags to just not include the problematic stuff automatically.