On Sat, Feb 28, 2015 at 03:43:24PM -0600, Bruce Dubbs wrote: > Guy Dalziel wrote: > > > >A note should be made that not using the recommended libarchive package will > >mean > >that the user will have to supply --no-system-libarchive to the bootstrap > >process > >in order to get this to work. > > > >Once this is specified then the bootstrap process goes through as normal. > > We assume that recommended dependencies are installed. If not, then the > user is on his own. We really can't document every situation where our > recommendations are not followed. > > -- Bruce > Yes. Sometimes recommended deps are there to make the package more useful, but nowadays most of them can be worked around with extra configure switches (if they cannot, the dep becomes required). And those of us who do omit them need to remember that if it breaks, we get to keep both pieces.
In this case, you presumably build a static libarchive into cmake, so you will need to remember that has been done if any libarchive vulnerability ever becomes known. As always, Your System, Your Rules. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
