Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 6281] optionally run make again on failure

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 6281] optionally run make again on failure
  • Date: Tue, 9 Mar 2004 00:19:35 -0500

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





------- Additional Comments From acedit AT armory.com 2004-03-09 00:19 -------
okay the past two attachments are a proof of concept for the BUILD split,
it can easily be expanded and needs some documentation in libapi etc.
The amount of actual new code comes out to about 5 lines, the rest is mostly
just gratuitous copying of code to leave the original implementation intact,
ideally some of that code (run_build and run_compile specifically) can be
refactored to minimize duplication.

I've tested every situation I can think of and the behavior should be
identical
to make a spell use the new style put
BUILD_STYLE=new
in DETAILS
then if there is a BUILD file put everything before prepare install
and the ') > $C_FIFO 2>&1' into a file name COMPILE (make it executable of
course),
and then put everything including and after prepare_install (and a leading
'(') in a file called
INSTALL.
you can look at real_default_compile and real_default_install for an example.
Of course if there is no BUILD file, you can change DETAILS; you'll see no
visible change,
but the code will follow the other path.

the next step is to rip a bunch of cast functions out into
/var/lib/sorcery/modules
perhaps in libcast or something, and then write that other script (mumble or
utter perhaps)
to provide access to that api



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page