On Fri, Dec 11, 2020 at 12:39:36PM -0600, Bruce Dubbs via blfs-dev wrote: > On 12/11/20 12:04 PM, Ken Moffat via blfs-dev wrote: > > > > 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. >
Sounds good. > > 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. In addition, my > scripts are instrumented to place logs and statistics in a consistent > location tagged by which host built the package. > My own systems take a very different approach in BLFS regarding dependencies - I work around avoiding some of the recommended deps, and add extra switches to use optional deps (e.g. I can look at jpegs and proably other graphics in links -g). > On the other hand, I find jhalfs invaluable for LFS. > > -- Bruce For LFS, my preference is to understand which packages use pesky static libs. But we know that (except for accidental errors) LFS-svn builds. My own BLFS builds of the set of packages I use are now less frequent (too much change for me to keep up with) and I've also started to build the whole of my normal desktop in chroot so that I can keep using the old desktop until everything has been compiled. I'm hopeful that blfs can be used to periodically build BLFS in chroot to uncover the new breakages. I suspect that I'll end up using jhalfs to build the LFS part as well for those test builds, but starting with a known good-enough LFS seemed the best initial approach. Like you, I'm not over-keen on re-downloading packages, but my download speed is adequate and my usage doesn't hit any caps, so I can live with that (particularly since I do not intend to run daily updates of the completed system). Meanwhile, I've downloaded at least four versions of firefox source this week (one beta, maybe two, I forget when the earlier one was done, and three release candidates) - that makes the mere 265MB of kf5 not very relevant. ĸen -- To say that it (his hair) was black and bound up in a ponytail is to miss the opportunity of using the term 'elephantine'. It was hair with personality. -- The Thief Of Time (about the monk, Sato). -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
