Package Details: i3-git 4.21.r4.g09670218-1

Git Clone URL: https://aur.archlinux.org/i3-git.git (read-only, click to copy)
Package Base: i3-git
Description: An improved dynamic tiling window manager
Upstream URL: http://i3wm.org/
Licenses: BSD
Groups: i3-vcs, i3
Conflicts: i3-gaps, i3-gaps-next-git, i3-wm
Provides: i3-wm
Submitter: Atsutane
Maintainer: Airblader
Last Packager: Airblader
Votes: 194
Popularity: 0.29
First Submitted: 2009-03-13 22:17 (UTC)
Last Updated: 2022-09-21 18:30 (UTC)

Required by (66)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 19 Next › Last »

<deleted-account> commented on 2016-10-03 10:20 (UTC)

After the recent update, this package segfaults on startup for me, whereas the i3-gaps-git does not.

Airblader commented on 2016-08-10 21:01 (UTC)

@blumsicle That part was pretty much just copied from the i3-wm package PKGBUILD. As far as i3-save-tree goes, that's a complete oversight. Thanks for pointing it out! I'll update all my i3 packages to use the single command.

blumsicle commented on 2016-08-10 20:03 (UTC)

I have a question about the PKGBUILD you created. In the original i3-git PKGBUILD, all the man pages are installed using a single command. However, in this one, you've elected to use an install command for each man page and, in the process, you've omitted the man page for the `i3-save-tree` command. Was this intentional or just an oversight? Also, thank you for the work you've put into this project as I can't see myself not using gaps anymore :)

pperduta commented on 2016-07-20 09:50 (UTC) (edited on 2016-07-20 09:51 (UTC) by pperduta)

Using this PKGBUILD I'm unable to clone i3 repo. I belive that line: `source=('git://github.com/Airblader/i3#branch=gaps')` should be changed to: `source=('git+https://github.com/Airblader/i3#branch=gaps')` as this works for me. I'm not sure if this is really broken, or it's just me (I'm behind proxy). If anyone has any information about this, please comment.

lutobler commented on 2016-05-08 19:33 (UTC) (edited on 2016-05-08 19:33 (UTC) by lutobler)

@badboy In the patch https://github.com/i3/i3/pull/2286/commits/7d20a6d11dc222237f5a76585a326313b03fc304 a new dependency on xcb-util-xrm was added, please add it, thank you!

Airblader commented on 2016-04-20 19:36 (UTC)

@ainola Too late. :-) I've pushed i3-gaps now which simply applies the patch to allow the out of tree build for now. I'd appreciate you giving it a shot and taking a look at the packaging.

ainola commented on 2016-04-20 19:27 (UTC)

@Airblader, I think the next release would be just fine. Considering your package has been happily used by the community for this long, now, I think there is no rush for this. Once again, thanks so much for maintaining!

Airblader commented on 2016-04-20 19:11 (UTC) (edited on 2016-04-20 19:14 (UTC) by Airblader)

@ainola Unfortunately in all currently releases versions, out of tree builds (like from the tarball) fail. This has been fixed, but only recently, so it's not yet in the current release. The way I see it we have a few options: * Wait for the next release before packaging i3-gaps (without -git). * Include the commit that fixed it as a patch for now and apply it before building. * Build from git for now and change that with the next release. However, I really would want to merge i3-gaps-git in this case. I don't really see any use in having a -git package for a branch which is 99% the same as the non-git package.

ainola commented on 2016-04-20 19:06 (UTC)

I think having both i3-gaps-git and i3-gaps is perfectly fine. As there are downloadable releases on Github's page, git would not be necessary: the source would just equal the tar.gz archive, which would then autoextract during the build process. -git packages are typically expected to follow the latest git releases, so I don't think anything needs to change here.

Airblader commented on 2016-04-20 18:59 (UTC)

@ainola Thanks for the hint, I'll look into fixing that. As for the release question, I guess it wouldn't hurt to make i3-gaps-git check out the actually tagged release (I'd keep i3-gaps-next-git the way it is, though), seeing how the branch rarely changes anyway (and I don't update pkgver between releases). But then the package name wouldn't really fit anymore, so I guess I'd have to publish i3-gaps as a new package and request them to be merged?

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 19 Next › Last »