Re: Moving packages from/to BLFS to/from LFS

I'm removing the discussion to keep this post to a reasonable level. See the previous 
posts in the thread to review the context.

I have already moved pcre2 from BLFS to LFS.

I plan on moving sqlite today.  The issue there is the documentation. There are 
several options:

1. Don't bother with the documentation.
2. Just add a comment that the docs are in zip format and the user can
    install them on their own after libarchive is installed in BLFS.
3. Create a tar.xz version of the documentation and place it on anduin.
4. Install libarchive.

This last option has a dependency chain:

libarchive  38
   libxml2   64
     icu     38
   lzo        6
   nettle     9
     valgrind
       5 optional dependencies

The numbers above are the counts of <xref>s in BLFS to the associated package.

If I move libarchive, I would also want to install libxml2, icu, and lzo.  I know we 
don't strictly need lzo, but it is a very short build that some users might want for
efficiency (speed) purposes.  I do not want to move valgrind to LFS because I think 
many users do not build it at all.  The nettle package is not needed at all here 
because libarchive can use openssl to do the same thing.

I'll note that any dependencies that are not added would be mentioned in Appendix C, 
Dependencies in the section 'Optional dependencies' for each package.

I am inclined to do option 3 above right now and think about libarchive and friends a 
little more.  However, to me, the number of explicit dependencies that can be removed 
from BLFS is a strong reason to do option 4.

   -- Bruce

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page