Randy McMurchy wrote: > Ken Moffat wrote these words on 03/10/08 18:28 CST: > >> Care to spell out your preferences ? To me, blfs has for long >> been somewhat pernickety about specifying sizes and SBUs in decimals. >> (I've always found some variation in my own build times, even for >> repeated builds when the cache should be "hot"). I'm happy to >> attempt to fit in with what I find, but a statement for "how small we >> ought to measure" would be useful. > > "Pernickity" ?? > > I had to look in the dictionary. *And you misspelled it* :-) > My dictionary has "persnickity", which would be the perfect word > in the context you used it. > > (don't you just love it when someone uses a word you haven't a > clue what it means, but they misspell it?) :-) > > Just messing with you, Ken > > > The Editor's Guide says one thing, and I didn't reference it, but > here is what *I* do (not that it is correct or right or the way it > should be or anything else): > > Tarball size: I don't even round it. I use 576kb if it isn't quite > a megabyte. If it is over a megabyte I use the entire integer side > and the first decimal of the fraction (e.g., 3,476,345 is 3.4 MB > in the book). > > Buildsize: I round to the nearest MB. Even if under 10 megabyte. > To me, 6.3 MB is the same as 6 MB. 205.6 is *always* 205. OpenOffice > is its own animal. I don't even know what it is, I don't build it > anymore (well I haven't in a long time, anyway). > > Buildtime: Rounded to the nearest one decimal fraction. No-brainer. > If I recall correctly, the Editor's Guide is the same on this one. > If over 10 SBU's I'd probably like to see it at an integer value, > though I can't guarantee how I've done it in the past. Use your > good judgment.
Well directly out of the Editor's guide: Units provided for the download sizes should be kilobytes (1024 bytes) or megabytes (1024 kilobytes). Entries less than a 1000 kilobytes should be specified as whole numbers (e.g., 320 KB); larger sizes should be accurate to one decimal (e.g., 6.9 MB). Build sizes should be rounded to the nearest megabyte and displayed as whole numbers (e.g., 38 MB). SBU entries should be rounded to one decimal. If the value is less than 0.1 SBU, it should be listed as "less than 0.1 SBU". Very long build times (greater than 10 SBUs) should be listed as integer values. What's wrong with that? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
