On 05/31/2015 09:17 PM, Pádraig Brady wrote: > On 31/05/15 18:15, Tomas Nordin wrote: >> I get confused about this, if not for else because all those utils are >> already on my system, so I guess I don't want to make a full install of >> the play code for trying it out. > > Off the top of my head: > > git clone --depth=1 git://git.sv.gnu.org/coreutils.git > cd coreutils > ./bootstrap && ./configure --quiet && make -j$(nproc) > git checkout -b my-branch > vim src/ls.c > make > # make install # to install to /usr/local/... by default > # (which is adjustable with ./configure options). > > See also: > http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=README-hacking;hb=HEAD > > If looking to send changes back upstream for inclusion see: > http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=HACKING;hb=HEAD
Regarding testing: you can run "make syntax-check" to see whether your changes comply with our coding standards; and you can run the testsuite with "make check" (or more of it with "make check-expensive" or "make check-very-expensive") to see if you introduced a regression. Finally you can add your own test case to the "tests/". Have a nice day, Berny
