Package Details: shifty-git 20140817-6

Git Clone URL: (read-only, click to copy)
Package Base: shifty-git
Description: Dynamic tagging library for Awesome window manager
Upstream URL:
Licenses: GPL2
Conflicts: shifty
Provides: shifty
Submitter: residentsummer
Maintainer: residentsummer
Last Packager: residentsummer
Votes: 46
Popularity: 0.000000
First Submitted: 2009-12-05 22:15 (UTC)
Last Updated: 2015-06-14 16:34 (UTC)

Latest Comments

1 2 Next › Last »

MarsSeed commented on 2022-02-25 23:08 (UTC)

GitHub is discontinuing git:// protocol access by mid-March.

Please kindly update URLs in source array to use git+https:// as protocol.

residentsummer commented on 2014-08-17 08:01 (UTC)

Oh, that's right, tuxitop. Updated pkgbuild. This change should be safe for "awesome-git" users, cos latter provides "awesome" anyway.

tuxitop commented on 2014-08-16 15:22 (UTC)

I wonder why "awesome-git" is still the dependecy, while there is "awesome" in the repositories and it's totally compatible with shifty.

residentsummer commented on 2013-07-29 17:28 (UTC)

Thanks, cdemoulins! Updated pkgbuild with proposed changes. To all: switched to more active repo (cdump's fork). Probably, you'll need to discard sources again (sorry for that).

cdemoulins commented on 2013-07-23 08:16 (UTC)

Could you please update your package using the new functionalities of makepkg like pkgver function, … See this PKGBUILD :

residentsummer commented on 2013-01-09 21:28 (UTC)

Updated package, please discard sources from previous builds.

residentsummer commented on 2013-01-02 13:15 (UTC)

Thanks, mickael! This one is good, I've contacted cdump for some details on stability.

mickael9 commented on 2012-12-30 20:54 (UTC)

Could you rather use this repository which seems compatible with awesome 3.5 ?

residentsummer commented on 2012-04-18 08:03 (UTC)

People, please read the whole discussion (it's just 3 elder comments; not so much, huh?) and, if you don't trust me, you can manually verify API incompatibility between unstable awesome (awesome-git) and bioe007's repo (all branches, even 'unstable', which meant to be version for unstable awesome). I won't switch to bioe007 unless it will be compatible with awesome-git. As for origin of residentsummer's repo, you can go there and read the README file.

seblu commented on 2012-04-17 23:24 (UTC)

Upstream repo seems to be inconsistent (as suggested by masterkorp) Awesome wiki (you $url) tell upstream is bioe007 git tree. Last commit on bioe007's trunk is 25 days ago (and commit are frequent) Last commit on residentsummer's trunk is 5 month ago in initial commit from residentsummer's trunk, there is the following line: +-- @author bioe007 <> So we can imagine residentsummer copy bioe007 stuff.