[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Does sed contain gnulib subdirectory when next release?

From: kk
Subject: Re: Does sed contain gnulib subdirectory when next release?
Date: Fri, 9 Jun 2017 13:23:33 +0800

Thanks for the detail tutorial!

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

> On Jun 9, 2017, at 00:55, kk <address@hidden> wrote:
> I see the release 4.4 from:
> The sed-4.4.tar.xz didn't contain gnulib subdirectory, but when I compile the sed master branch form:
> 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,
 - assaf

reply via email to

[Prev in Thread] Current Thread [Next in Thread]