On Wed, Jan 23, 2019 at 10:33:58PM -0600, Bruce Dubbs via blfs-dev wrote: > > I will create a demo version of what I am talking about after you make the > rustc update. I'll also send you my build script for comparison/review. >
That idemo would be helpful, but you know that my scripts are *very* different. If I'm feeling nasty I might even send you my 'functions' script - it contains a lot of historical baggage. > > > It also makes it easy to remove a test installation without polluting > > > /usr. > > > I note that rustc-1.32.0-src/install is 716M. On my system right now > > > ~/.cargo is 747M so this package has the largest installed footprint of > > > any > > > > 295M /home/lfs/.cargo > > 295M /home/ken/.cargo > > 294M /home/ken/.cargo-base1331 > > 295M /home/ken/.cargo-base1320 > > > > I was testing all the packages which use rust, to see how much (if > > anything) they downloaded. Here, user lfs does the automated > > installs but I do a lot of test builds manually. > > Seems the logical thing to do. > > > So, I wipe out .cargo before a new build. This also lets me test > > how long is spent downloading cargo files by rust - only a minute or > > so with a decent network connection, in SBU terms it is lost in the > > rounding. > > I thought about that. I'll test it that way. > [...] > > And I though I was the one who worried about disk space ;-) > > Worried? No. But I do pay attention. My default LFS partition size in the > past has been 10G with separate partitions for /tmp, /home, /opt, /boot, but > I am finding that building everything in BLFS makes things too tight for > space. For my next full build, I will use larger partitions. > > -- Bruce Because I keep older systems around for some time, I never used separate /opt. When I started installing full TL I had to bind some space in /opt. My current partitioning for desktop systems uses 25GB for '/' and tmpfs for /tmp (usually too small for big packages, but building elsewhere saves things across reboots). I have not yet repartitioned my haswell, that only has about 20GB : it gets tight (but with kde and gnome built for testing, even 25GB might get a bit pokey). If I ever get round to QA builds with jhalfs I'll probably use *much* bigger filesystems for that - but I won't have to worry about the backup space for that. But many hardware changes are needed before I can get to there, it might not happen. ĸen -- thread 'main' panicked at 'giraffe', /tmp/rustc-1.32.0-src/src/test/run-fail/while-panic.rs:17:13 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
