Changeset 2870 for trunk/packages


Ignore:
Timestamp:
Jan 10, 2010, 2:53:58 AM (15 years ago)
Author:
broder
Message:

I can spell, I promise.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/packages/invirt-dev/README.invirtibuilder

    r2869 r2870  
    2727  Because of how Git tracks history, it's better suited for tracking a
    2828  series of small repositories, as opposed to one large one
    29   [#]_. Furthermore, most pre-existing tools and techniques for
    30   dealing with Debian packages in Git repositories (such as
    31   git-buildpackage_ or `VCS location information`_) are designed
    32   exclusively for this case.
     29  [#]_. Furthermore, most preexisting tools and techniques for dealing
     30  with Debian packages in Git repositories (such as git-buildpackage_
     31  or `VCS location information`_) are designed exclusively for this
     32  case.
    3333
    3434* Synchronization between Git and APT repositories.
     
    9393For the Invirt_ project's use of the Invirtibuilder, we adapted our
    9494existing configuration mechanism. Our configuration file consists of a
    95 singls YAML_ file. Here is the snippet of configuration we use for our
     95single YAML_ file. Here is the snippet of configuration we use for our
    9696build configuration::
    9797
     
    173173was a separate build queue where each build request was handled and
    174174processed independently of any requests before or after it. It's not
    175 possible to have these semantics using Git as a signalling mechanism
     175possible to have these semantics using Git as a signaling mechanism
    176176without breaking standard assumptions about how remote Git
    177177repositories work.
     
    186186the build and adds it to the build queue. Because of the structure of
    187187remctl's ACLs, we are able to have different ACLs depending on which
    188 pocket the build is destined for. This allows us to fulfil our design
     188pocket the build is destined for. This allows us to fulfill our design
    189189goal of having different ACLs for different pockets.
    190190
     
    297297and our untrusted development environment. In order to be trusted for
    298298the production environment, the Invirtibuilder needs to run in the
    299 production environment as well. However, it would be disasterous if
     299production environment as well. However, it would be disastrous if
    300300access to the development environment allowed a developer to insert
    301301malicious packages into the production apt repository.
Note: See TracChangeset for help on using the changeset viewer.