On 5/11/19 11:51 AM, William Harrington via blfs-dev wrote:

On May 11, 2019, at 08:36, Xi Ruoyao via blfs-dev 
<[email protected]> wrote:

On 2019-05-11 08:27 -0500, William Harrington wrote:
On May 11, 2019, at 02:33, Xi Ruoyao via blfs-dev <


Greetings,

Is it possible that someone will go directly to netlibs and filter back to a
previous package? How about if they want a program that isn't in BLFS that
needs cmake and the deps. I don't understand the idea that cmake isn't needed.
Seems like it should be as a recommended or optional dep when going thru BLFS.
Name a distro that doesn't have cmake.

Yes it is needed.  Nobody wants to remove it from the book.  But if a package
*can* be built with autotools or meson, why should we build it with cmake and
introduce a hard dependency?

Because it is in transition. Eventually autotools won't be needed.

That's a long 'eventually'. I doubt that gnu projects, especially like glibc or gcc, will change in the near to mid future.

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to