Package Details: gn-git r1523.377ad041-1

Git Clone URL: https://aur.archlinux.org/gn-git.git (read-only)
Package Base: gn-git
Description: Meta-build system which generates Ninja build files
Upstream URL: https://gn.googlesource.com/gn
Keywords: build chromium gn ninja
Licenses: BSD
Conflicts: gn, gn-bin
Provides: gn
Submitter: aperez
Maintainer: aperez (zopieux)
Last Packager: aperez
Votes: 4
Popularity: 0.122231
First Submitted: 2015-09-14 18:50
Last Updated: 2019-01-16 12:03

Required by (9)

Sources (2)

Latest Comments

1 2 Next › Last »

aperez commented on 2018-12-02 19:26

@Jake: Good point, I have added “gn” in the list of conflicting packages as suggested. Thanks!

Jake commented on 2018-12-02 12:03

Please add 'gn' (community repo) to the conflicts array, because it also installs /usr/bin/gn and provides is not enough for pacman to automatically resolve this.

aperez commented on 2018-08-24 14:42

@fightcookie: Now that's weird... I always run “git clean && makepkg -fs” to double check that things build fine before pushing an update. And currently the version is extracted just fine ¯_(ツ)_/¯

fightcookie commented on 2018-08-14 14:45

pkgver() fails with plain makepkg and pacaur and therefore the version stays at the same and aur helpers always think there is an update available:

==> Starting pkgver()... fatal: not a git repository: '/home/xuiqzy/test/gn-git/gn' fatal: not a git repository: '/home/xuiqzy/test/gn-git/gn' ==> Updated version: gn-git r.-1

selmf commented on 2018-07-28 12:09

@petronny: That issue was already fixed in the last update the package received.

petronny commented on 2018-07-27 06:19 

[234/235] LINK gn
[235/235] LINK gn_unittests
?[1m?[32m==>?(B?[m?[1m Entering fakeroot environment...?(B?[m
?[1m?[32m==>?(B?[m?[1m Starting package()...?(B?[m
install: cannot stat 'gn/tools/gn/docs/*.md': No such file or directory
?[1m?[31m==> ERROR:?(B?[m?[1m A failure occurred in package().?(B?[m

Please fix this.

aperez commented on 2018-07-25 01:35

@selmf: Agreed, I think the “gcc-support.patch“ is small enough that it should not be a problem, so for the moment I would like to keep it. If nobody runs into issues with it (or Gn builds done with it applied and using GCC) maybe I'll submit it upstream later on.

@petronny: That issue should be fixed now.

petronny commented on 2018-07-24 07:43

Cannot find the git package needed to handle git sources. Please fix this.

selmf commented on 2018-07-23 19:35

I think we should try to avoid 'overpatching' gen.py. The standalone version of gn is still quite new compared to the old bootstrap method which made previous versions of this package fairly unpredictable. Anything that goes beyond simple adjustments should probably be done (or submitted) upstream to avoid later breakage.

aperez commented on 2018-07-22 17:10

I agree with @selmf that the patch suggested by @bm456 does not seem to make much sense in this case. If something, what I could do is adding some bits to pick the values of CFLAGS/CXXFLAGS/LDFLAGS from the environment, and in that way the settings from “makepkg.conf” would be used for building.