If nothing has changed in the book, there is no need to regenerate
version.ent, blfs-full.xml, etc... So only make version.ent
.PHONY if REV has changed.
We will change pythonhosted.xml to incorporate all python modules
(perhaps excepting PyXDG) at https://files.pythonhosted.org
and move it to the top of the Python Modules page.
We will need to place the md5sums for the module sources in packages.ent
so they can be referenced in two places.
For now, remove the page from the build. Later we will need to clean up
Makefile and archive stylesheets/{pyhosted-inc,pythonhosted}.xsl.
Created a new file, dummy.xml, that is copied to
./general/prog/python-dependencies/pythonhosted.xml
if that file does not already exist. This avoids a warning
when generating the book for the first time after
cloning the source from the repository.
This branch introduces a new layout for python modules, similar
to what is done for perl modules. This allows to have useful python
modules in the book (sphinx, pytest, requests, gi-docgen), together
with their dependencies.
As a convenience for users who build by hand, a "Building
pythonhosted.org Files" section is added, which allows building all
the python modules dependencies in one go. It is generated from
the individual module pages, so the authoritative instructions are
on those individual pages.
- Add `locked-deps = true` and `vendor = true`. These allows building
the package w/o downloading from crates.io (the bootstrap compiler
still needs to be downloaded though), and eliminates the necessity of
using a DESTDIR installation. Note that in LFS we already do DESTDIR
installation for ncurses so we won't lose too much educational
material.
- Add `description = "for BLFS &version;"` so BLFS version will show up
in the output of `rustc --version`.
- Remove `rpath = false`. With rpath we can skip the modification of
`/etc/ld.so.conf` file. Note that rpath is coded as
`$ORIGIN/../lib`, so if you run `ldd` on the executable in the build
directory, it will show the path to the build directory; but if you
run `ldd` on the installed executable, it will show the correct path
to the installed library. See `man ld.so` for more information about
`$ORIGIN`.
This option is not needed for recent versions of gnutls, as
the build system does exactly what is expected: link binaries and
libraries with rpath pointing to the build tree at first, then
remove rpath completely when relinking at install time.