D0 Code - Pulling new versions

1. /usr/products comes from ftp://fnkits.fnal.gov/. All you need to do is:

   > setup upd
   > upd list -aK+      # will show you all products and all versions available
                        # (the K+ shows the information all on one line so you can
                        #  pipe to grep, sort etc)
   > upd list -aK+ <product>      # to get a listing of just <product>
   > upd install <product> <version> [-G"-c"]
   

   The value in "[]" says to declare it "current" on your machine. Everything else is taken care of by either the database at the distribution node or your own updconfig. If you don't want to declare it current at this time, leave that clause off the command. In that case, when you do want to declare it "current"

   > ups declare -c <product> <version>
   

   This assumes that your flavor of Operating System is one that is supported by FNAL. If it isn't, we'll have to do something else. That topic is well beyond the scope of this document (and I haven't a clue as to what we'd do about it!)

2. /d0usr/products come from the D0 distribution node, www-d0.fnal.gov. Yes, that's our web server! In this case the commands are exactly the same, with the addition of "-h www-d0.fnal.gov" to the "upd list" and "upd install" commands.

   > upd list -aK+ -h www-d0.fnal.gov
   > upd list -aK+ -h www-d0.fnal.gov <product>
   > upd install -h www-d0.fnal.gov <product> <version> [-G"-c"]
   

3. /d0dist/dist is our main code repository and it too is distributed from www-d0.fnal.gov. The same commands work here too. Once again the "-h www-d0.fnal.gov" switch needs to be used, as in the /d0usr/products case. There are a few other major differences as well, due to the differences between a "normal" product and a SoftRelTools product:
   • Normally, you'll pull over the D0RunII (and D0RunII-bin) product. This will pull over all the source code packages that are part of it (over 400 of them). You can pull the individual source code packages if you wish.
   • In addition to specifying D0RunII and it's version you need to specify which "SRTflavor" you want/need. This is done via the "-q" switch.
     • "D0RunII -q dist" will pull over the "NULL" version. That is, the basic structure. You'd then have to build it at your site. This must be done if your machine doesn't match in type and OS version one of the "officially supported" D0 platforms, or does match it but the code hasn't yet been ported to it.
     • "D0RunII-bin -q <SRTflavor-compiler>" to get a particular SRT flavor/compiler combination. The format of the "SRTflavor-compiler" name is that used by SoftRelTools,
       ie) IRIX6-KCC_3_4, Linux2-KCC_3_4 or CYGWIN32_NT4-MSVC50 etc. This is different from the "flavor" used by UPS and UPD. See the UPS documentation for details.
       NOTE: the three above are normally available prebuilt.

   > upd list -aK+ -h www-d0.fnal.gov D0RunII
             # to see what versions of D0RunII are available
   > upd list -aK+ -h www-d0.fnal.gov D0RunII-bin
             # to see what binary versions of D0RunII are available
   > upd install -h www-d0.fnal.gov <version> -q dist D0RunII
             # to get the skeleton to build locally
   > upd install -h www-d0.fnal.gov D0RunII-bin <version> -q Linux2-KCC_3_4
             # to get the Linux version including binaries.
    etc.
   

   Different SRTFlavors can be overlaid on top of each other. If you need to do that just repeat the last command for each SRTFlavor you need. UPD will only download the parts that haven't already been done, the binary pieces.