juliendehos commented on this pull request.
> @@ -0,0 +1,33 @@
+# Template file for 'tup'
+pkgname="tup"
+version="0.7.5"
+revision=1
+hostmakedepends="fuse-devel pkg-config"
Yes. Tup's building is boostrapped: a shell script builds tup on the host then the host uses this build to cross-build tup for the target. So fuse-devel is necessary for both builds.
juliendehos commented on this pull request.
> @@ -0,0 +1,33 @@
+# Template file for 'tup'
+pkgname="tup"
+version="0.7.5"
+revision=1
+hostmakedepends="fuse-devel pkg-config"
+makedepends="fuse-devel sqlite-devel"
+depends="sqlite"
+short_desc="File-based build system"
+maintainer="Julien Dehos <dehos@lisic.univ-littoral.fr>"
+homepage="http://gittup.org/tup/index.html"
+license="GPL-2"
+distfiles="https://github.com/gittup/${pkgname}/archive/v${version}.tar.gz"
+checksum="361b3e069308ce1d9505d1cb927999ac448811a3425c724123e0c48602a9d1e4"
+nostrip_files="tup"
Building fails without this line ("ERROR: tup-0.7.5_1: non-PIE executable found in PIE build: /usr/bin/tup").
Honestly, I don't understand that perfectly; if you have any idea...
cr6git commented on this pull request.
> @@ -0,0 +1,33 @@
+# Template file for 'tup'
+pkgname="tup"
+version="0.7.5"
+revision=1
+hostmakedepends="fuse-devel pkg-config"
Seems like that changed in the latest release: https://github.com/gittup/tup/releases/tag/v0.7.6
````
- Added a bootstrap-nofuse.sh script that avoids using FUSE during bootstrap for restricted environments
````