defaria.com/blogs/Status/archives/week_2004_12_26.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
  11
  12    <title>Status for Andrew DeFaria: December 26, 2004 - January  1, 2005 Archives</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/week_2004_12_19.html" title="December 19, 2004 - December 25, 2004" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/week_2005_01_02.html" title="January  2, 2005 - January  8, 2005" />
  17 </head>
  18 <body class="layout-one-column">
  19    <div id="container">
  20       <div id="container-inner" class="pkg">
  21
  22          <div id="banner">
  23             <div id="banner-inner" class="pkg">
  24                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  25                <h2 id="banner-description">Searchable status reports and work log</h2>
  26             </div>
  27          </div>
  28
  29          <div id="pagebody">
  30             <div id="pagebody-inner" class="pkg">
  31                <div id="alpha">
  32                   <div id="alpha-inner" class="pkg">
  33
  34                      <p class="content-nav">
  35                         <a href="http://defaria.com/blogs/Status/archives/week_2004_12_19.html">&laquo; December 19, 2004 - December 25, 2004</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/week_2005_01_02.html">January  2, 2005 - January  8, 2005 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">December 30, 2004</h2>
  44                      <a id="a000267"></a>
  45                      <div class="entry" id="entry-267">
  46                         <h3 class="entry-header">More documentation</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50
  51 <p><li>Yet more documenting of Build, Test, Release processes</li></p>
  52
  53 </ul>
  54
  55                               <p class="entry-footer">
  56                                  <span class="post-footers">Posted by  at  5:27 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000267.html">Permalink</a>
  57
  58
  59                               </p>
  60                            </div>
  61                         </div>
  62                      </div>
  63
  64
  65
  66                      <h2 class="date-header">December 29, 2004</h2>
  67                      <a id="a000266"></a>
  68                      <div class="entry" id="entry-266">
  69                         <h3 class="entry-header">Documentation</h3>
  70                         <div class="entry-content">
  71                            <div class="entry-body">
  72                               <ul>
  73
  74 <li>Spent most of the day documenting <a href="http://saturn.lynx.com/build/">Build/Test/Release</a> processes</li>
  75
  76 </ul>
  77
  78                               <p class="entry-footer">
  79                                  <span class="post-footers">Posted by  at 10:09 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000266.html">Permalink</a>
  80
  81
  82                               </p>
  83                            </div>
  84                         </div>
  85                      </div>
  86
  87
  88
  89                      <h2 class="date-header">December 28, 2004</h2>
  90                      <a id="a000265"></a>
  91                      <div class="entry" id="entry-265">
  92                         <h3 class="entry-header">Releasing 5.0.0</h3>
  93                         <div class="entry-content">
  94                            <div class="entry-body">
  95                               <ul>
  96
  97 <li>Attempting to archive this 5.0.0 build both toolchain and lynxos. Not really sure where everything comes from or goes to</li>
  98
  99 <li>More work on cmptags.pl</li>
 100
 101 </ul>
 102
 103                               <p>Directories, builds, dated directories, etc are all over, spead out between t3, dopey, t-k1g-1, etc.. It's hard to know where things are and where they need to end up. Will look into this tomorrow with Thu</p>
 104
 105 <p>Regarding cmptags.pl, rearranged this to attempt to produce a simple list like:</p>
 106
 107 <pre>
 108 ECR Number ####
 109       path/to/foo.c            1.30
 110       path/to/bar.c            1.2.3.1
 111 </pre>
 112
 113 <p>Unfortunately this appears to be very slow to process. cmptags.pl does not attempt to optimise things only working on files recently updated, rather it goes though all of the files in CVS and generates, parsed and creates data structures for all the CVS info, even that which it's not particularly interested in at the momment so that it can be more generally used. This takes forever with CVS as each file must be found and a cvs log issued and output parsed. Unlike Clearcase there doesn't seemto be a cvs command line prompt so cvs is constantly being invoked (process overhead) and it's always talking to the server (network overhead) and there's a lot of data (tags, revisions, comments, etc) to be processed. Clearly CVS has not been optimized for this sort of access.</p>
 114
 115 <p>Not sure how or if this can be optimized any further. It's a shame because I'm almost at the point where I can ask "Show me the files and version numbers for the following ECR's" which is something I know I'm gonna need quickly here for the impending build note that needs to be created.</p>
 116
 117                               <p class="entry-footer">
 118                                  <span class="post-footers">Posted by  at  7:05 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000265.html">Permalink</a>
 119
 120
 121                               </p>
 122                            </div>
 123                         </div>
 124                      </div>
 125
 126
 127
 128                      <h2 class="date-header">December 27, 2004</h2>
 129                      <a id="a000264"></a>
 130                      <div class="entry" id="entry-264">
 131                         <h3 class="entry-header">Fix Copyright, native 3.2.2/5.0.0 build</h3>
 132                         <div class="entry-content">
 133                            <div class="entry-body">
 134                               <ul>
 135
 136 <li>Modified fix_copyright.pl to take into account the situation where the LynuxWork copyright is contained inside a comment block with another company's copyright.</li>
 137
 138 <li>Was able to build 3.2.2/5.0.0 toolchain natively by booking to the ide.0c partition</li>
 139
 140 <li>Build of non-development los178 is successful with expected errors</li>
 141
 142 </ul>
 143
 144                               <p class="entry-footer">
 145                                  <span class="post-footers">Posted by  at  9:36 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000264.html">Permalink</a>
 146
 147
 148                               </p>
 149                            </div>
 150                         </div>
 151                      </div>
 152
 153                   </div>
 154                </div>
 155             </div>
 156          </div>
 157       </div>
 158    </div>
 159 </body>
 160 </html>