Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 15946] size of TMPFS should be possible to set in DETAILS

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 15946] size of TMPFS should be possible to set in DETAILS
  • Date: 20 May 2011 07:49:50 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=15946


Thomas Orgis <sobukus AT sourcemage.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |sobukus AT sourcemage.org




--- Comment #1 from Thomas Orgis <sobukus AT sourcemage.org> 2011-05-20
02:49:47 ---
I'd rather see a DETAILS variable named BUILD_SIZE, specifying how much
storage
will be needed during the build. This would not be specific for tmpfs, only.
I'd expect mk_source_dir to do that:

1. If tmpfs is desired, check if there's enough RAM (twice as much?) to
accomodate BUILD_SIZE. Bonus is for checking the actual free amount of memory
(minus buffers). If yes, mount and be done.
2. If tmpfs won't work out, check if there's enough disk space free. At least
warn if that's not the case, perhaps even abort.


Added bonus will be support for out-of-tree builds. Then one needs a size cap
for the sources and the build separately. But it might be a good idea to
integrate creation of the usual $SOURCE_DIRECTORY.bld into the API, anyway. Or
... eh ... those spells could just work in $SOURCE_DIRECTORY/source and
$SOURCE_DIRECTORY/build ... why complicate matters with two tmpfs mounts?

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



  • [SM-Sorcery-Bugs] [Bug 15946] size of TMPFS should be possible to set in DETAILS, bugzilla-daemon, 05/20/2011

Archive powered by MHonArc 2.6.24.

Top of Page