On 06/01/2017 07:14 AM, Avinash Sonawane wrote: > On Thu, Jun 1, 2017 at 3:10 AM, L A Walsh <[email protected]> wrote: > >> What's the point of a tar that needs online access? > > While building, Wget2 fetches the latest current version of Gnulib > from Savannah. Bundling the Gnulib with Wget2 compressed archive might > get you a stale, outdated version of Gnulib. :)
The tar file that Gitlab (and also Github) automatically provides is just a tar of the git repo ! It is not the same as what is generally known as "distribution tarball", which includes all needed gnulib stuff and which doesn't need a './bootstrap'. We didn't make a release yet, to there is no distribution tarball available. Maybe we could generate one automatically via Gitlab CI and provide it for download ... that makes building for non-developers much easier. >> Looks like wget2 is "infected" with the gnulib virus. > > No. Gnulib is a very cool library which keeps the code shared by many > GNU packages at one central location which helps to make the packages > more modular. > > Additionally, Gnulib makes porting a package much easier and that's > how you can use Wget2 on Windows platform even if the primary dev > machines are Linux boxes. :) > >> Hmmmm....this is not very easy to build... >> >> (sigh). > > No. Building Wget2 is very easy. It just requires 4-5 commands. That's it! > > Please take a look at "Building from git" section in the README.md[0]. > And just remember to use https url to clone the repo if you don't want > to deal with SSH keys. I'm reiterating it here just for the > completeness sake: > $ git clone https://gitlab.com/gnuwget/wget2.git > > [0] https://gitlab.com/gnuwget/wget2/blob/master/README.md With Best Regards, Tim
signature.asc
Description: OpenPGP digital signature
