Re: Does sed contain gnulib subdirectory when next release?

[kk]

Thanks for the detail tutorial!

On Fri, Jun 9, 2017 at 1:11 PM, Assaf Gordon <address@hidden> wrote:

Hello,

> On Jun 9, 2017, at 00:55, kk <address@hidden> wrote:
>
> I see the release 4.4 from:
>
>     https://ftp.gnu.org/gnu/sed/sed-4.4.tar.xz
>
> The sed-4.4.tar.xz didn't contain gnulib subdirectory, but when I compile the sed master branch form:
>
>     http://git.savannah.gnu.org/cgit/sed.git/
>
> It is necessary to use gnulib, so I want to ask does sed contain gnulib subdirectory when next release?

When building from a tar archive (e.g. 'sed-4.4.tar.xz'),
the required gnulib modules are already contained in
the archive under the "./lib" directory.

Effectively, the 'sed-4.4.tar.xz' is self-sufficient,
you don't need any other piece of code to build sed
(only shell, make, and a C compiler are needed).


When building from the git repository, it is implicitly
assumed you are a developer (as opposed to a non-developer
who just wants to build sed).
As such, it requires more programs (e.g. automake/autoconf),
and also downloads the entire git repository for gnulib.

That way, sed's files are stored in the git repository
and gnulib files are stored in the gnulib git repository -
without the need to duplicate the gnulib files in sed's repository.


When building from a git repository, the steps are roughly:
1. git clone from sed's repository
2. ./bootstrap
   2.1. bootstrap will then 'git clone' from gnulib's repository
   2.2. bootstrap runs the gnulib's setup,
        which copies the needed files to ./lib
   2.3. bootstrap will run automake + autoconf
3. ./configure
4. make

When building from tar archive, only "./configure" and "make" are needed.
The "bootstrap" steps are already pre-stored in the archive.

Hope this helps,
regards,
 - assaf