Package Details: ly-git v0.3.0.r0.g61fd099-1

Git Clone URL: https://aur.archlinux.org/ly-git.git (read-only, click to copy)
Package Base: ly-git
Description: TUI display manager
Upstream URL: https://github.com/cylgom/ly
Licenses: custom:WTFPL
Conflicts: ly, python-ly-git
Submitter: cylgom
Maintainer: cylgom
Last Packager: cylgom
Votes: 8
Popularity: 1.10
First Submitted: 2017-05-23 22:29
Last Updated: 2019-06-10 15:10

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

loserMcloser commented on 2020-02-01 20:40

Please add

backup=('etc/ly/config.ini')

to the PKGBUILD.

4le34n commented on 2019-11-12 04:33

Invalid file permissions /etc/ly/config.ini /etc/ly/lang/*.ini

Add to PKGBUILD:

chmod 644 ${pkgdir}/etc/ly/config.ini

chmod 644 ${pkgdir}/etc/ly/lang/*.ini

tkrizek commented on 2019-06-04 16:04

There's no need to include inih.git and termbox-next.git in sources, since they're git submodules of ly.git

LeonisCuriosity commented on 2019-03-10 14:34

Pour les compatriotes !

cylgom commented on 2018-09-26 13:53

@dreieck: done, thank you for reporting @lll2yu: I'm figuring out how things work, sorry for inconvenience :p

lll2yu commented on 2018-09-24 03:21

EDIT:- Fixed with new update

fails to build

==> Starting prepare()...
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 0.2-1-gce56ce4

dreieck commented on 2018-09-03 12:10

Should conflict with the package python-ly, as both install the file /usr/bin/ly.

cylgom commented on 2017-11-07 20:42

I just tried to make a full update and it fixed the issue. As it included a new version of the ncurses package, I assume something was broken on their side and they fixed it. Sorry for the inconvenience and late answer :(

160R commented on 2017-11-05 00:39

It compiles after installing "ncurses-full"

runical commented on 2017-11-04 20:44

I can confirm that this error detuur mentioned also occurs for me (in a clean chroot). Is there anything that can be done to solve this?