William Harrington wrote:
On Tue, 26 Jan 2016 17:29:10 -0600 Bruce Dubbs <[email protected]>
wrote:
Should we add pcre to LFS? Both less and grep can use it and the
only optional dependency is valgrind.
There are 21 packages in BLFS that list it as a dependency.
It's a small package (1.5 MB, 0.3 SBU).
Hello Bruce,
Along with PCRE, ACL and ATTR are useful at the get go as a few
packages in a base build use them.
Although, for a base system, should we only include required deps? I
know acl and attr were left over from when LFS sysvinit and LFS Systemd
book were trying to have one book. If we go with the reasoning of a lot
of packages in BLFS list it as a dependency, we would end up adding
Python, libxsml2, libxslt, an ssl library and who knows what else to
the base build.
I do know that after building LFS/BLFS a few times, a user will
eventually know what they need and what order to do it. The great thing
about LFS is we let the user figure out what they want in a base build
and the devs keep the base build minimal.
The reason I was considering adding pcre to LFS was to avoid users having
to rebuild grep and less later if they want pcre capabilities. The BLFS
dependencies are a side effect, but that wasn't the primary reason.
To be honest, I've never found that I wanted pcre capabilities in grep or
less. The only reason I even noticed was in running the tests for grep in
the public beta. I do use preg_replace and preg_match a lot in php though.
I did notice in the LFS dependencies appendix that Xorg and CUPS are
listed for grep. I could find no reference for them in the beta and will
remove those when the next stable grep is released.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
