# The form data below was edited by matt_attaway
# Perforce Public Depot Jobs
#
# Job: The job name. 'new' generates a sequenced job number.
# Status: Job status; [open/closed/suspended]. Required
# Project: The project this job is for [none/cdsp4/jam/p4hl] Optional.
# Severity: [A/B/C] (A is highest) Required.
# ReportedBy The user who created the job. Can be changed.
# ReportedDate: The date the job was created. Automatic.
# ModifiedBy: The user who last modified this job. Automatic.
# ModifiedDate: The date this job was last modified. Automatic.
# OwnedBy: The owner, responsible for doing the job. Optional.
# Description: Description of the job. Required.
# DevNotes: Developer's comments. Optional.
Job: job000013
Status: closed
Project: jam
Severity: C
ReportedBy: miklos_fazekas
ReportedDate: 2002/02/25 17:17:20
ModifiedBy: matt_attaway
ModifiedDate: 2014/02/09 23:30:28
Description:
TOGETHER targets not removed on failure
From: http://maillist.perforce.com/pipermail/jamming/2002-January/001537.html :
| If an actions fails it's targets are delted by jam.
| If the action is marked with TOGETHER it's targets are not deleted. Why?
|
| I'd like them to be deleted.
|
| Code from make1.c
| > /* If the command was interrupted or failed and the target */
| >/* is not "precious", remove the targets */
| >
| >if( status != EXEC_CMD_OK && !( cmd->rule->flags & RULE_TOGETHER ) )
| >{
| > LIST *targets = lol_get( &cmd->args, 0 );
| >
| > for( ; targets; targets = list_next( targets ) )
| >if( !unlink( targets->string ) )
| > printf( "...removing %s\n", targets->string );
| >}
|
| Is !( cmd->rule->flags & RULE_TOGETHER ) neccesary here?!
|
| Reagards,
| Miklos