On 10/5/19 12:46 AM, Kevin Buckley via lfs-dev wrote:
In the Chapter 6 Python XML source,
1) there's a block of commands rendered as
chmod -v 755 /usr/lib/libpython3.7m.so
chmod -v 755 /usr/lib/libpython3.so
ln -sfv pip3.7 /usr/bin/pip3
which come from the following XML
chmod -v 755 /usr/lib/libpython&python-minor;m.so
chmod -v 755 /usr/lib/libpython3.so
ln -sfv pip3.7 /usr/bin/pip3</userinput></screen>
Could that last one not mke use of the &python-minor; entity too ?
Yes it could, but that only would be meaningful if/when python updates
to 3.8 or later if that line is not manually updated.
ln -sfv pip&python-minor; /usr/bin/pip3</userinput></screen>
2) there's a line
<term><option>--no-same-owner</option> and --no-same-permissions</term>
so should the second option not be delineated within <option> tags ?
For internal consistency, I suppose so, but functionally it is not
meaningful.
In the Chapter 6 IPRoute2 source, it says
It is also necessary to disable building two modules that requires
http://www.linuxfromscratch.org/blfs/view/9.0/postlfs/iptables.html.
sed -i 's/.m_ipt.o//' tc/Makefile
however, there is no note as regards the fact that once/if IPTables
has been built in BLFS, one could come back and rebuild IPRoute2
without that modification.
Indeed, if one has IPTables, SHOULD IPRoute2 be rebuilt with
those modules ?
It depends on if they are needed. The book mentions iptables and gives
a reference, so rebuilding is implied. The affected modules are for the
tc application so they seen pretty exotic to me.
This might be yet another package that could be in a "Reinstalling
LFS packages for a BLFS system" section of the BLFS Book, along
with Shadow.
Perhaps. You can probably add grep after pcre to that list. Would you
like to write that section?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
