Package Details: awesome-git 4.3.1347.ga1f58ab97-1

Git Clone URL: https://aur.archlinux.org/awesome-git.git (read-only, click to copy)
Package Base: awesome-git
Description: Highly configurable framework window manager
Upstream URL: http://awesome.naquadah.org/
Licenses: GPL2
Conflicts: awesome
Provides: awesome, notification-daemon
Submitter: noonov
Maintainer: trollixx (actionless)
Last Packager: actionless
Votes: 227
Popularity: 0.35
First Submitted: 2007-11-22 16:01 (UTC)
Last Updated: 2022-02-02 23:15 (UTC)

Dependencies (25)

Required by (54)

Sources (1)

Pinned Comments

actionless commented on 2024-07-06 04:53 (UTC)

ldoc just got updated in the mirror i use from 1.5.0-1 to 1.5.0-2 and i see the same messsage if trying to start ldoc - so just downgrade to 1.5.0-1

trollixx commented on 2016-12-27 08:30 (UTC)

Please do not flag this package out-of-date unless it fails to build due to upstream changes.

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 Next › Last »

noonov commented on 2011-05-14 13:51 (UTC)

*IMPORTANT* Latest version of awesome-git is NOT able to build with xcb-util<=0.3.6. So, now you have to have xcb-util>=0.3.8 and some new packages below: - xcb-util 0.3.8, xcb-util-image 0.3.8, xcb-util-keysyms 0.3.8, xcb-util-wm 0.3.8 Libraries provided by xcb-util<=0.3.6 are splitted into several packages. - Patched version of startup-notification 0.10 for xcb-util>=0.3.8 src tarballs for pacman here: xcb-util 0.3.8-1 http://www.fileserve.com/file/RvgmMEQ xcb-util-image 0.3.8-1 http://www.fileserve.com/file/4YYZ6YD xcb-util-keysyms 0.3.8-1 http://www.fileserve.com/file/sjuanGr xcb-util-wm 0.3.8-1 http://www.fileserve.com/file/N24R4SF startup-notification 0.10-3 http://www.fileserve.com/file/AdtmSrv Feel free to modify, submit, maintain or mirror these packages. (Of cource binary packages are welcome.) xcb-util in [extra] is already flagged as out-of-date, but still not updated to 0.3.8. Please be patient.

hellnest commented on 2011-02-21 15:44 (UTC)

There's a patch for current CMake issue. Please put it inside your PKGBUILD, thx https://awesome.naquadah.org/bugs/index.php?getfile=384

<deleted-account> commented on 2011-02-19 17:57 (UTC)

A change in the semantics of cmake from 2.8.3 to 2.8.4 makes the build fail currently. see upstream bug FS#869. https://awesome.naquadah.org/bugs/index.php?do=details&task_id=869.

root_op commented on 2011-01-21 19:40 (UTC)

Just wanted to point out something regarding awesome4, people might experience some issues with getting transparency from compositors to work, this is due to that awesome now creates and manages clients with a new method different from what it used before. What it now does is basicly forcefully gain parenting of the client. This however removes the 32bit color depth support (Not sure why but ask on #awesome@oftc if in doubt). This has however been resolved by making use of ARBG in X. There was vary result from this however, some experienced rendering artifacts and some didn't at all. Although it's disabled by default. To get to the point: If you want or require transparency through the additional 8bit alpha channel then prepend the argument -a or --no-argb to awesome. (Awesome-git should really get it's own wikipage since master/head is Awesome4)

svenstaro commented on 2010-12-03 19:07 (UTC)

Getting an error during make while making manpages. Looks like an upstream fault.

<deleted-account> commented on 2010-09-29 19:06 (UTC)

The bug report I filed has been closed and is fixed with a recent commit. It appears this was a problem with LuaDoc that may or may not have been intended; either way it will never be changed because LuaDoc is no longer developed. A link to the commit is below. I've built the package and it compiles just fine. http://git.naquadah.org/?p=awesome.git;a=commit;h=787bdbe4684340407ce7b36c51005405f9ab620f

<deleted-account> commented on 2010-09-23 17:02 (UTC)

Also you can disable luadoc generation to solve this issue (which is still here) by passing -DGENERATE_LUADOC=false to cmake.

<deleted-account> commented on 2010-09-18 20:18 (UTC)

I submitted the following bug report: http://awesome.naquadah.org/bugs/index.php?do=details&task_id=823&project=1

<deleted-account> commented on 2010-09-18 16:49 (UTC)

Thank you!

<deleted-account> commented on 2010-09-18 03:38 (UTC)

The problem was introduced in the latest commit. For now you can add the following just before 'msg "GIT checkout done or server timeout"' to get the last good commit. msg "Reverting to previous good commit" cd ${_gitname} git checkout -b latestgoodcommit c368b848176d3201f4763101de0de544fa7be7b5 cd ..