no_unres_co.pl trigger should be regarded as a special case

Bug #531201 reported by Lars Kruse
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Accelerated ClearCase
Fix Committed
Medium
Jens Brejner

Bug Description

The install params in the no_rec_co.pl trigger reads:

our %install_params = (
    "name" => $TRIGGER_NAME, # The name og the trigger
    "mktrtype" => "-element -all -preop checkout,unreserve", # The stripped-down mktrtype command
    "supports" => "bccvob,ucmvob", # csv list of generic and/or custom VOB types (case insensetive)
);

But this feature is kind of odd, and should be isolated to only nnDocVob s (as in named_brtypes_only.pl) something like this:

our %install_params = (
    "name" => $TRIGGER_NAME, # The name og the trigger
    "mktrtype" => "-element -all -preop checkout,unreserve", # The stripped-down mktrtype command
    "supports" => "nnDocVOB", # csv list of generic and/or custom VOB types (case insensetive));

Lars Kruse (lakruzz)
Changed in acc:
assignee: nobody → Lars Kruse (lak-praqma)
assignee: Lars Kruse (lak-praqma) → Jens Brejner (jbrejner)
Revision history for this message
Jens Brejner (jbrejner) wrote :

That makes sense.

Jens Brejner (jbrejner)
Changed in acc:
status: New → In Progress
importance: Undecided → Medium
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.