Changes between Version 1 and Version 2 of CustomControlFields


Ignore:
Timestamp:
07/01/15 13:35:51 (9 years ago)
Author:
jdreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CustomControlFields

    v1 v2  
     1Occasionally, we may not want to build a package for certain releases or suites, either because we don't need it, or it doesn't make sense. 
    12 
     3There are two control file fields we use for this: 
    24 
    3 We use nobuild files to indicate releases we shouldn't build a package for. They sit in the directory you run da* from. So, for instance 
     5* `X-Debathena-Build-For` - A space-separated list of codenames (e.g. `trusty`, `precise`).  The package will **ONLY** be built for those releases and no others. 
     6* `X-Debathena-No-Build` - A space-separated list of codenames that the package will **NOT** be built for. 
    47 
    5 builder@zulu:/mit/debathena/packages/config/debathena-cluster-login-config$ cat nobuild 
    6 etch lenny squeeze 
    7  
    8 They're not kept in version control anywhere, which is unfortunate. You also have to edit them when you add a new release if the package shouldn't be built for that release.  
    9  
    10 '''TODO: Except we don't, docuyment X-Debathena-No-Build and friends''' 
     8It is not a syntax error to have both fields, but it's entirely pointless.