Hi,
On Mon, 26 Aug 2019, Jean-Marc Pigeon via blfs-dev wrote:
My worry (Hoping to be paranoiac) and this concern the book:
- Libreoffice Book directives are such, that 77 components are
added/downloaded within external/tarballs directory, this
between the configure phase and the build phase.
(please could you confirm this fact from your side).
We (the book) have no real control/say about those components
(version, contents, function).
Depending on which part of that worries you most, there might be an easy
solution. I do not like that behavior of packages to download arbitrary
stuff during build either. My main concern is not that I don't actually
know every packages function, but that it is neither useful to download
the same set of tarballs a second time at all (for building a second time
or on a second machine, especially with limited network access) nor
even having to think about the risk of getting something else downloaded
the next time.
Therefore, for packages like libreoffice (and ISTR apache-ant), I let the
build process download its stuff once, integrate only those downloads into
an otherwise untouched source folder and repackage and keep this extended
package including what it would download rather than the original. So my
libreoffice-6.3.0.4++.tar.xz (352MB) has a fetch.log and 77 archives/fonts
in its external/tarballs and builds from that do not download anything...
Uwe
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
