Re: gnulib build/test ?

[Tim Rühsen]

Hi Bruno,

On 05/17/2017 10:15 AM, Bruno Haible wrote:
> Hi Tim,
> 
> +#### Contributor's Quick Start Guide ####
> 
> This does not belong in the README. The README is for first-time *users*.
> For first-time *contributors*, many GNU packages have a HACKING file,
> but gnulib already has a doc section "Contributing to gnulib".

I considered that, but thought that *users* are in fact *developers* and
thus potential *contributors*. Anyways, if you move that text into
HACKING (or sort of) it would let interested developers jump in quick
(that's why there is *Quick* in the title), first starting a browser to
search for the needed information might be too tedious for some people.
('Hackers' are known to be lazy when it comes to reading docs).

> +Note the difference between --dir=../testdir1 and --dir=/tmp/testdir1 : The 
> former is on the
> +same file system as the gnulib checkout, and uses hard links to the .c and 
> .h files; therefore
> +for quick edits of only .h and .c files you can do the edits in the testdir
> 
> This is not in a state where we could document it: Unfortunately it does not
> work with the 'kate' editor (it breaks hard links when saving with backup).
> I need to try how it works with symlinks instead.

Hard links are not portable and you hardly find software that does 'the
right thing', especially not editors that normally do backups and/or
saving into temp files + moving. Symlinks might be a problem as well.
Good luck.

With Best Regards, Tim

signature.asc
Description: OpenPGP digital signature