Re: [Gretl-users] Git updating

On Mon, 26 Oct 2015, Clive Nicholas wrote: Well, "sudo" is not normal in this context! Clive, what are you trying to commit? Have you made any changes to the sources? These "untracked" files (and there will be _many_ of them) were generated in the course of your build. They are not primary source files and don't belong in the git repository. You don't have write permission on the sourceforge gretl-git repository; and moreover you don't have anything to commit/push. That's relevant only if you are a developer with new code or revisions to make available. As someone just building gretl from git to be bang up-to-date, the only git command you'll need is "git pull" from time to time, to update your local copy of the sources. The cleanest way to keep the generated files separate from the ones under version control (i.e. that belong in git) is to build "out of tree". Instead of doing ./configure and make inside gretl-git, you can create a parallel directory -- say, gretl-build: cd into that and (assuming the two directories are at the same hierarchical level), do ../gretl-git/configure <your options> make [etc.] That way the git sources will remain pristine. Alternatively, to the same effect, you can create your build directory inside the gretl-git directory, as in: cd gretl-git mkdir build cd build ../configure <your options> make [etc.] In the second case you can create a text file ~/.config/git/ignore with content: build/ and git will ignore the contents of your build directory rather than reporting them as "untracked". Meanwhile, "make clean" will get rid of many of the generated files in the git tree itself. ("make distclean" ought to do a more comprehensive job, but I see it's not working properly; that's something we need to fix.) Allin