*Synopsis*: Standard file exclusion mechanism needed for Cadmium tools

CR 6800164 changed on Feb 27 2009 by <User 1-5Q-8204>

=== Field ============ === New Value ============= === Old Value =============

See Also               6763564                                                
SR 1-488021004
 Functionality         Secondary                                              
 Hardware              generic                                                
 Impact                Significant                                            
 Operating System      solaris_nevada                                         
 Product Name          solaris                                                
 Product Release       solaris_nevada                                         
 Severity              3                                                      
====================== =========================== ===========================

     
*Change Request ID*: 6800164

*Synopsis*: Standard file exclusion mechanism needed for Cadmium tools

  Product: solaris
  Category: consolidation
  Subcategory: os-net-tools
  Type: RFE
  Subtype: 
  Status: 10-Fix Delivered
  Substatus: 
  Priority: 4-Low
  Introduced In Release: 
  Introduced In Build: 
  Responsible Engineer: <User 1-28L01W>
  Keywords: 

=== *Description* ============================================================
I have been working on a new Cadmium command, 'hg mapfilechk' as
part of:

    6785284 Mapfile versioning rules need to be more visible to gatelings

In the course of that work, have encountered the need to specify
a list of files that should be excluded from processing. Cadmium has
a .NOT mechanism which would suffice, except that the .NOT files
are not gate-specific. We need a mechanism that allows different
gates to maintain exclusion lists that apply to their own files.
Although I could create a mapfilechk-specific mechanism, this is
a general need, and a general solution that applies to all the cadmium
tools would be better.

I propose to create a directory at the top level of a mercurial
workspace named 'exception_lists'. Within this directory, files
with the same name as the cadmium tool they apply to can be created
to specify file exclusions. The format of these files is identical
to that of the .NOT files, and cadmium uses the same implementation
to process them internally.

The initial file in 'exception_lists' will be 'mapfilechk', to be
integrated with 6785284.

*** (#1 of 1): 2009-02-02 17:46:23 GMT+00:00 <User 1-28L01W>


=== *Public Comments* ========================================================

=== *Workaround* =============================================================

=== *Additional Details* =====================================================
        Targeted Release: solaris_nevada
        Commit To Fix In Build: snv_109
        Fixed In Build: snv_109
        Integrated In Build: snv_109
        Verified In Build: 
  See Also: 6763564, 6785284, 6798660
  Duplicate of: 
  Hooks:
        Hook1: 
        Hook2: 
        Hook3: 
        Hook4: 
        Hook5: 
        Hook6: 
  Program Management: 
  Root Cause: 
  Fix Affects Documentation: No
  Fix Affects Localization: No

=== *History* ================================================================
        Date Submitted: 2009-02-02 17:46:22 GMT+00:00
        Submitted By: <User 1-28L01W>

        Status Changed    Date Updated                  Updated By
        7-Fix in Progress 2009-02-05 23:59:54 GMT+00:00 <User 1-28L01W>
        8-Fix Available   2009-02-10 16:49:21 GMT+00:00 <User 1-5HNZ8F>
        10-Fix Delivered  2009-02-25 18:30:02 GMT+00:00 <User 1-5Q-3253>


=== *Service Request* ========================================================
        Impact: Significant
        Functionality: Secondary
        Severity: 3
        Product Name: solaris
        Product Release: solaris_nevada
        Product Build: 
        Operating System: solaris_nevada
        Hardware: generic
        Submitted Date: 2008-10-24 13:55:14 GMT+00:00


=== *Service Request* ========================================================
        Impact: Limited
        Functionality: Primary
        Severity: 3
        Product Name: solaris
        Product Release: solaris_nevada
        Product Build: 
        Operating System: solaris_nevada
        Hardware: generic
        Submitted Date: 2009-02-02 17:46:23 GMT+00:00


=== *Multiple Release (MR) Cluster* - 0 ======================================


Reply via email to