Armin K. wrote:
On 12/10/2014 12:28 PM, Armin K. wrote:
On 12/09/2014 08:33 PM, [email protected] wrote:
Author: fernando
Date: Tue Dec 9 11:33:19 2014
New Revision: 15177
Log:
Rebuilt Thunderbird-31.3.0, now at runlevel 3, and got a more satisfactory and
reliable SBU.
Modified:
trunk/BOOK/xsoft/other/thunderbird.xml
Modified: trunk/BOOK/xsoft/other/thunderbird.xml
==============================================================================
--- trunk/BOOK/xsoft/other/thunderbird.xml Tue Dec 9 11:19:25 2014
(r15176)
+++ trunk/BOOK/xsoft/other/thunderbird.xml Tue Dec 9 11:33:19 2014
(r15177)
@@ -11,7 +11,7 @@
<!ENTITY thunderbird-md5sum "3781dfb541412c7f6b530a654b834ce5">
<!ENTITY thunderbird-size "164 MB">
<!ENTITY thunderbird-buildsize "3.6 GB (68 MB installed)">
- <!ENTITY thunderbird-time "30 SBU (using parallelism=4)">
+ <!ENTITY thunderbird-time "16 SBU (using parallelism=4)">
]>
<sect1 id="thunderbird" xreflabel="Thunderbird-&thunderbird-version;">
As you can see, this largely depends on what's running on the system.
Why bother upgrading it this much? I only check it each major release.
Seems like too much work.
Don't get me wrong though, I have nothing against you doing this, but
doesn't it make it little less true for someone? I mean, obviously the
former value was from a system under (average) load and the second one
is from a sort of base system with no additional software running. Why
not add these two, then divide them by two to get a value that's mostly
true for base system and systems under (average) load (ie, a wm, desktop
or simply just X).
For me, updating size and time are free. I have standard scripts that
automatically print out md5sum, size, build size, ans SBU for each run.
Thee is no reason not to update these values.
OTOH, if other things are happening on the system while a package is
building, the build size and SBU values can be thrown off. That's one
reason why I use a separate development system.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
