On Fri, 2020-12-11 at 12:39 -0600, Bruce Dubbs via blfs-dev wrote: > On 12/11/20 12:04 PM, Ken Moffat via blfs-dev wrote: > > On Fri, Dec 11, 2020 at 11:03:05AM -0600, Bruce Dubbs via blfs-dev > > wrote: > > > On 12/11/20 12:40 AM, Pierre Labastie via blfs-dev wrote: > > > > On Fri, 2020-12-11 at 02:43 +0000, Ken Moffat via blfs-dev > > > > wrote: > > > > > > > > > > Yes I've been bitten by that when trying to build LXQt. Note > > > > that it > > > > has nothing to do with jhalfs. Either put Attic instead of > > > > stable, or > > > > use a later version. > > > > > > Of course with a later version of kf5/plasma all the md5sums are > > > different. > > > > > > -- Bruce > > > > For plasma in particular, do not the dependencies (and perhaps even > > the available tarballs) change over time, so that we ought to stick > > to the current versions of both for the moment ? > > > > More generally, our releases are frozen at a point in time, and > > subject to errata. If a url becomes unusable, do we not fix that > > in the development book and add an erratum ? > > Most of the blfs packages we use are copied to > http://ftp.osuosl.org/pub/blfs/ as they are upgraded. An exception > to > that is kf5/plasma due to the number of packages and their size. The > size of the repository there is now 220G and has packages there going > back to BLFS-6.1 (2008). I do update osuosl virtually every day. > > What I think is appropriate is for this case is to add a note similar > to > the one in ImageMagick, but point it to Attic instead. > > > Pierre has explained to me on alfs-discuss about the jhalfs issue > > with kf5, I'll maybe come back to that next week. > > I do not use jhalfs for building BLFS. It is useful for showing the > order to build dependencies, but I have a long history of having BLFS > sources and scripts in /usr/src/<package>. jhalfs does not support > that > organization and I do not want to re-download sources I already have.
Just a note that I think this is possible with jhalfs (not tested much, because I do not have that layout): in envars.conf, set: export JH_SRC_ARCHIVE=/usr/src export JH_SRC_SUBDIRS=1 this should allow to have sources in /usr/src/<package>. Of course, the scripts wouldn't reside there, since jhalfs creates its own scripts on the fly. > In addition, my scripts are instrumented to place logs and statistics > in > a consistent location tagged by which host built the package. Interesting. Right now the "work" directory (it contain the logs) can be manually moved to any location at the end of the build (that's what I do), but this could be automated and instrumented with some information (date, host, ...?). > > On the other hand, I find jhalfs invaluable for LFS. > > -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
