Package Details: slim-git

Git Clone URL: (read-only, click to copy)
Package Base: slim-git
Description: Desktop-independent graphical login manager for X11 (git)
Upstream URL:
Licenses: GPL2
Conflicts: slim
Provides: slim
Submitter: Cinelli
Maintainer: bidulock
Last Packager: bidulock
Votes: 64
Popularity: 0.000000
First Submitted: 2012-12-19 04:30 (UTC)
Last Updated: 2015-12-15 18:15 (UTC)

Latest Comments

commented on 2019-01-24 16:59 (UTC)

CMake Error: No source or binary directory provided

bidulock commented on 2016-03-19 22:38 (UTC)

WorMzy's repo is more up to date and contains fixes for systemd installation needed by Arch.

thwald commented on 2016-03-19 22:28 (UTC)

you should use the official git repo:

WorMzy commented on 2014-06-18 06:43 (UTC)

I interpret that to mean that the tag and the revision should be easily discernible, which I feel is achieved by using underscores. Incidentally, pacman treats periods and underscores the same way, i.e. they're interchangeable, so no epoch is needed for this change. $ vercmp 1.1.1 1.1_1 0 In any case, I avoid using epoch on AUR packages, as I feel it encourages reliance on AUR helpers.

bidulock commented on 2014-06-17 23:03 (UTC)

Well, see the VCS PKGBUILD Guidelines on the wiki: You should prefix the last component with an 'r' and use '.' between all components. Also, when changing the numbering format for a package, you should bump the epoch= value in the PKGBUILD so as to avoid pacman treating the newer version as an outdated version.

WorMzy commented on 2014-06-17 11:40 (UTC)

I'd prefer not to. I felt that was confusing, and made it appear as though the commits (4) was part of the tag (1.3.6). Do you have any reasoning to support the use of periods over underscores, or is it just personal preference?

bidulock commented on 2014-06-17 11:33 (UTC)

Please change pkgver() in PKGBUILD back from: echo $(git describe --tags) | sed -e 's:v::' -e 's:-:_:g' to echo $(git describe --tags) | sed -e 's:v::' -e 's:-:.:g' Note the underscore vs. dot.

WorMzy commented on 2014-06-16 09:59 (UTC)

I hadn't noticed that. I've uploaded a mirror to github and pointed the PKGBUILD at it for now. If anyone knows of an active mirror/fork, please let me know and I'll update the PKGBUILD to use it.

maltem commented on 2014-06-10 12:44 (UTC)

Apparently the hosting site (Berlios) shut down its services in January 2014. Does anyone know if there's still an upstream maintainer?

erikw commented on 2013-10-22 17:21 (UTC)

Also, why not use the official up-to-date git repo?

erikw commented on 2013-10-22 17:05 (UTC)

In PKGBUILD:37 there is one dot too much.

WorMzy commented on 2013-10-07 11:03 (UTC)

They've been merged for six months now, you just need to modify slim-git's PKGBUILD to explicitly tell CMake that you wanted to build slimlock too. An updated version of slim (with slimlock) hit extra/ last week, so it conflicts with slimlock{,-git} whether it explicitly says it does (conflicts/provides) or not. I was deliberating opening a bug report/general gripe about the official slim package not having provides=('slimlock'), but I'm not sure it's really a bug, since the AUR is unsupported, and slimlock's never been in the official repositories anyway. That's a good catch about the optdepend, I'd forgotten about that. I'll remove that. As it stands, slim-git and slimlock-git should be able to peacefully coexist, I'll look into why they don't, if they don't. I'd deliberately ommitted slim-git from the conflicts array because it (so far) hasn't conflicted. I'll update this package in a bit, I'm currently suffering from some DNS troubles on my landline. :(

tealeaf commented on 2013-10-07 08:17 (UTC)

I know that slim and slimlock are now (apparently) being merged, so I can see why slimlock-git would want to conflict with slim(-git). Right now, though, two things: 1) This has slim as an optional dependency, but also as a conflict. That seems bizarre. 2) The slim and slim-git packages don't provide slimlock yet. This means that it's currently not possible to actually have slim(-git) and slimlock-git installed without editing the PKGBUILD. (Unless I've made a mistake somewhere.) Could we remove the conflict with slim until the slim or slim-git packages are actually providing slimlock?

Diego commented on 2013-06-02 18:40 (UTC)

also slimlock from now is based on dannyn repo

WorMzy commented on 2013-05-22 23:13 (UTC)

Heads up to anyone receiving notifications, I've changed the versioning scheme to something more appropriate than just the date you built the package. If you're using an AUR helper, this will probably appear as a "downgrade".

WorMzy commented on 2013-03-22 02:22 (UTC)

Well this is an interesting development. I don't personally agree with it, but I'm happy for Joel, at least. Thanks for the heads-up, Diego. I'll pass on the message to Dannyn, in case he wants to push his changes to the slim repo. I still believe that slimlock deserves to be a package in it's own right, for people who want a lightweight screen locker, but don't necessarilly use slim. So I'll continue maintaining this package for as long as the upstream git repo can build a stand-alone slimlock binary. I'll stick to Dannyn's repo for now, as it's the most up-to-date.

Diego commented on 2013-03-22 00:51 (UTC)

the merge between slim and slimlock is started;a=commit;h=fccae89bbf97eb77b3c7a6c55b37ffa9c60eeaee Someone could tell to dannyn?

Diego commented on 2013-03-13 15:05 (UTC)

Sorry... i'm confused today...

WorMzy commented on 2013-03-13 14:57 (UTC)

? I updated the PKGBUILD to use dannyn's github a few months ago.

Diego commented on 2013-03-13 14:49 (UTC)

Please update this package with the new git mantainer or disown the package

eworm commented on 2013-03-08 12:57 (UTC)

Sure... Just use slim-git. ;)

haawda commented on 2013-03-08 12:45 (UTC)

The git repo is more recent than the svn repo of slim.

Cinelli commented on 2013-01-31 20:50 (UTC)

service file added.

browntown commented on 2013-01-24 02:23 (UTC)

Looks like it was me, I changed a curl parameter as a workaround for another package (dmg2img) and when the extra parameter was removed slimlock installed. My bad.

wilbowma commented on 2013-01-23 19:02 (UTC)

@browntown, I'm also getting errors. It looks like when yaourt downloads it (at least on this machine), it's not downloading the .tar.gz file properly. It's actually returning an HTML file. >cd /tmp/.../aur-slimlock-git > md5sum slim-archlinux-simple.tar.gz 77415a56a56b2574be1926a82263dbe5 slim-archlinux-simple.tar.gz > cat slim-archlinux-simple.tar.gz | curl -F 'sprunge=<-' I fixed this by changing the source URL for the .tar.gz to the 'direct link' given by source forge:

dannyn commented on 2013-01-23 04:07 (UTC)

looks good to me. copy/paste the error maybe. source=('slimlock-git.install' 'slim.conf' '') md5sums=('40af4379e8b17203414356edbf57469f' '3f75d2a7a85c08a41b2f75eeb548cd87' '7c7aaa255561444a4ae3e9f1dfb4be5d') ~/slimlock-git/src $ md5sum slimlock-git.install slim.conf slim-archlinux-simple.tar.gz 40af4379e8b17203414356edbf57469f slimlock-git.install 3f75d2a7a85c08a41b2f75eeb548cd87 slim.conf 7c7aaa255561444a4ae3e9f1dfb4be5d slim-archlinux-simple.tar.gz

WorMzy commented on 2013-01-09 22:14 (UTC)

The problem with that is that you need a /etc/slim.conf for slimlock to read to get it's configuration, and having the slimlock package provide it means that it'd conflict with the slim package. I've had a think while I've been away, and I've decided that it's best to install an example slim.conf and a basic theme to /usr/share, and then prompt the user to either install slim to have everything work out of the box, or copy the example slim.conf to /etc and configure it themselves. There's loads of slim themes in the AUR that the user can use if they don't like the default, and it makes it more obvious that just because it's 'slimlock', doesn't mean it can't be used with other login managers.

dannyn commented on 2013-01-09 03:06 (UTC)

How about the installer installing a theme there by default if there isnt anything there yet?

WorMzy commented on 2013-01-08 00:38 (UTC)

I disagree. You can create /etc/slim.conf and a theme manually and and it'll work whether slim is installed or not. The slim binary is never used, and there's no shared libraries in the slim package that slimlock needs. I might add it to the optdepends, or include an .install explaining how to get it to work without installing slim though.

FreeAsInGimme commented on 2013-01-07 23:20 (UTC)

Like 3V0LU710N said a while back, slim needs to be added as a dependency. Without it, running slim lock yields "Failed to open default theme file /usr/share/slim/themes/default/slim.theme."

WorMzy commented on 2013-01-02 11:08 (UTC)

Cheers for the heads up, I've updated the PKGBUILD.

dannyn commented on 2013-01-02 03:41 (UTC)

I've renamed the repo to Got a couple of more fixes coming soon too.

3V0LU710N commented on 2012-05-27 22:54 (UTC)

Please add 'slim' to the depends array... =)