Changeset 2870 for trunk/packages
- Timestamp:
- Jan 10, 2010, 2:53:58 AM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/packages/invirt-dev/README.invirtibuilder
r2869 r2870 27 27 Because of how Git tracks history, it's better suited for tracking a 28 28 series of small repositories, as opposed to one large one 29 [#]_. Furthermore, most pre -existing tools and techniques for30 dealing with Debian packages in Git repositories (such as31 git-buildpackage_ or `VCS location information`_) are designed32 exclusively for thiscase.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. 33 33 34 34 * Synchronization between Git and APT repositories. … … 93 93 For the Invirt_ project's use of the Invirtibuilder, we adapted our 94 94 existing configuration mechanism. Our configuration file consists of a 95 singl sYAML_ file. Here is the snippet of configuration we use for our95 single YAML_ file. Here is the snippet of configuration we use for our 96 96 build configuration:: 97 97 … … 173 173 was a separate build queue where each build request was handled and 174 174 processed independently of any requests before or after it. It's not 175 possible to have these semantics using Git as a signal ling mechanism175 possible to have these semantics using Git as a signaling mechanism 176 176 without breaking standard assumptions about how remote Git 177 177 repositories work. … … 186 186 the build and adds it to the build queue. Because of the structure of 187 187 remctl'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 design188 pocket the build is destined for. This allows us to fulfill our design 189 189 goal of having different ACLs for different pockets. 190 190 … … 297 297 and our untrusted development environment. In order to be trusted for 298 298 the production environment, the Invirtibuilder needs to run in the 299 production environment as well. However, it would be disast erous if299 production environment as well. However, it would be disastrous if 300 300 access to the development environment allowed a developer to insert 301 301 malicious packages into the production apt repository.
Note: See TracChangeset
for help on using the changeset viewer.