6 Commits

Author	SHA1	Message	Date
Adam Strzelecki	6cc9853935	bootstrap: Generate final install.sh during build ... This solves problem where bootstrap was simply copying ./install.sh.template into ./install.sh. Then first call of ./install.sh was calling ./koch install that was running extra compilation and overwriting ./install.sh with new content. This was overcomplicated, and also caused first `sudo ./install.sh DIR` to run compilation under root account, leaving root owned files in working directory. Now bootstrap calls `./koch geninstall` that just generates ./install.sh without calling it. This ./install.sh is FINAL one, and running it does not generate any files aside passed DIR. This makes whole process simpler.	2015-10-03 19:51:17 +02:00
Araq	6c256ddcae	cause I have no life	2015-06-10 11:50:08 +02:00
Araq	1b98d32579	no private deprecated symbols	2015-06-10 11:11:29 +02:00
Adam Strzelecki	7909591d41	Bring back (again) bootstrap.sh executable bit ... Reverts "bootstrap.sh: cannot keep exec bit on windows" commit 2d2eca18b8. We do not need to remove executable bits to workaround old msysGit bug that shows files having executable bits as modified. This can and should be addressed by msysGit user either by using latest version that will treat `bootstrap.sh` as having executable bit because of UNIX Shebang presence, or setting Git config's `core.fileMode` to false. See: http://stackoverflow.com/questions/12193020/file-mode-with-msysgit http://www.grumpydev.com/2011/01/19/switching-from-cygwin-to-msysgit-git-thinks-everything-has-been-modified/ Quoting Git manual: core.fileMode If false, the executable bit differences between the index and the working copy are ignored; useful on broken filesystems like FAT. See git-update-index(1). True by default.	2015-06-05 14:00:27 +02:00
Araq	2d2eca18b8	bootstrap.sh: cannot keep exec bit on windows	2015-05-28 12:59:40 +02:00
Sergey Avseyev	b77ae66e84	Get rid of git submodule	2015-05-26 14:16:22 +03:00