defaria.com/blogs/Status/archives/000265.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: Releasing 5.0.0</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/000264.html" title="Fix Copyright, native 3.2.2/5.0.0 build" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000266.html" title="Documentation" />
  17
  18
  19
  20
  21
  22    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  23 </head>
  24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  25    <div id="container">
  26       <div id="container-inner" class="pkg">
  27
  28          <div id="banner">
  29             <div id="banner-inner" class="pkg">
  30                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  31                <h2 id="banner-description">Searchable status reports and work log</h2>
  32             </div>
  33          </div>
  34
  35          <div id="pagebody">
  36             <div id="pagebody-inner" class="pkg">
  37                <div id="alpha">
  38                   <div id="alpha-inner" class="pkg">
  39
  40                      <p class="content-nav">
  41                         <a href="http://defaria.com/blogs/Status/archives/000264.html">&laquo; Fix Copyright, native 3.2.2/5.0.0 build</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000266.html">Documentation &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000265"></a>
  47                      <div class="entry" id="entry-265">
  48                         <h3 class="entry-header">Releasing 5.0.0</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52
  53 <li>Attempting to archive this 5.0.0 build both toolchain and lynxos. Not really sure where everything comes from or goes to</li>
  54
  55 <li>More work on cmptags.pl</li>
  56
  57 </ul>
  58                            </div>
  59                            <div id="more" class="entry-more">
  60                               <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>
  61
  62 <p>Regarding cmptags.pl, rearranged this to attempt to produce a simple list like:</p>
  63
  64 <pre>
  65 ECR Number ####
  66       path/to/foo.c            1.30
  67       path/to/bar.c            1.2.3.1
  68 </pre>
  69
  70 <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>
  71
  72 <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>
  73                            </div>
  74                         </div>
  75                         <p class="entry-footer">
  76                            <span class="post-footers">Posted by  on December 28, 2004  7:05 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000265.html">Permalink</a>
  77                         </p>
  78                      </div>
  79
  80
  81
  82
  83                   </div>
  84                </div>
  85             </div>
  86          </div>
  87       </div>
  88    </div>
  89 </body>
  90 </html>