Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - i3-gaps-git

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: i3-gaps-git 4.13-2

Git Clone URL: https://aur-dev.archlinux.org/i3-gaps-git.git (read-only)
Package Base: i3-gaps-git
Description: A fork of i3wm tiling window manager with more features, including gaps
Upstream URL: https://github.com/Airblader/i3/tree/gaps
Keywords: gaps i3
Licenses: BSD
Groups: i3-vcs
Conflicts: i3-gaps, i3-gaps-next-git, i3-git, i3-wm, i3bar, i3bar-git
Provides: i3-wm
Submitter: aminb
Maintainer: Airblader
Last Packager: Airblader
Votes: 73
Popularity: 5.849113
First Submitted: 2015-01-04 04:34
Last Updated: 2016-11-09 07:32

Required by (14)

Sources (1)

Latest Comments

1 2 3 Next › Last »

Airblader commented on 2016-11-09 07:32

@ssmATarch Yeah, forgot about that. Thanks!

ssmATarch commented on 2016-11-09 01:40

@Airblader Do you want to add xcb-util-xrm as a dependency, because it doesn't build otherwise (reports missing 'xcb-xrm')?

pperduta commented on 2016-07-20 09:50

Using this PKGBUILD I'm unable to clone i3 repo. I belive that line:
should be changed to:
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.

Airblader commented on 2016-04-20 19:36

@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

@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

@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

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

@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?

ainola commented on 2016-04-20 18:41

Thanks for maintaining this!

A few things:

1) You should quote your variables to prevent word splitting. All these install commands would fail if someone were to build this in "My Dir".

2) Are you willing to maintain a stable, non-git version of this? As you're the dev I don't want to tread on your efforts by packaging the stable releases if you intend to, but I would rather be running releases than git versions on my machine :).

Airblader commented on 2016-04-01 19:42

@johnwind I have no idea what you mean, but please report (potential) bugs on Github, not here.