https://bugzilla.redhat.com/show_bug.cgi?id=1022283 --- Comment #8 from Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> --- (In reply to Ralf Corsepius from comment #7) > (In reply to Zbigniew Jędrzejewski-Szmek from comment #5) > > It is nice to be able to use it without bundling in the sources: > No. This is not the way gnulib is supposed to be used. > gnulib files are supposed to be updated from git and the results to be > bundled inside of a source-tree. This is one of the approaches. Another one is to update those sources regularly during development(gnulib-tool --update), and only release releases with a specific snapshot. But even assuming that gnulib files are copied and kept in tree, as you say, there's a question how to best do that. During normal development of C code, if I'm about to gnulib-ify my project, it is much more continent to say 'yum install gnulib && gnulib-tool --import', than to say 'cd /var/tmp/ && git clone <some-address-I'll-have-to-look-up> && make -C gnulib && cd - && $OLDPWD/gnulib/gnulib-tool --import'. For the developer, keeping gnulib git tree updated is an additional chore, which is nicely solved by updating the gnulib snapshot through yum. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review