defaria.com/blogs/Status/archives/000406.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: portgd/3.0.0 build</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/000405.html" title="build_los178 scripts" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000407.html" title="Build scritps/web" />
  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/000405.html">&laquo; build_los178 scripts</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000407.html">Build scritps/web &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000406"></a>
  47                      <div class="entry" id="entry-406">
  48                         <h3 class="entry-header">portgd/3.0.0 build</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52   <li>Ported changes from LOS178 20050801/20050806 -> GD</li>
  53
  54   <li>Built TOT for LOS178 3.0.0</li>
  55 </ul>
  56                            </div>
  57                            <div id="more" class="entry-more">
  58                               <h3>portgd</h3>
  59
  60 <p>Was asked to port the changed from LOS178 -> GD again. As this is a frequent occurance it screams for automation. As I had already coded a verifycrs, which essentially automates verification of ported [E}CRs from one repository to another, it seems a simple case to derive as script to do the porting. Coded up portgd. Note that portgd does not perform automatic building - just porting of the files associated with the passed in [E}CRs.</p>
  61
  62 <h3>build_los178_343</h3>
  63
  64 <p>Changed build_los178_343 to go back to using scp to obtain the toolchain tarball. This is still kludgy because it entails hardcoding the location (which is date based) of the source tarball. However, using NFS requires that the NFS area is accessible and in the past it was an automount point to an assumed -hosts map location. That doesn't work on Linux systems using autofs (an investigation of using amd instead of autofs has not yet been performed). As such, from a Linux system, the toolchain tarball was not easily accessible via NFS. So we're back to using scp, which has it's own problems, namely the assumption that passwordless scp access has been set up.</p>
  65                            </div>
  66                         </div>
  67                         <p class="entry-footer">
  68                            <span class="post-footers">Posted by  on August 15, 2005 11:50 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000406.html">Permalink</a>
  69                         </p>
  70                      </div>
  71
  72
  73
  74
  75                   </div>
  76                </div>
  77             </div>
  78          </div>
  79       </div>
  80    </div>
  81 </body>
  82 </html>