| 1 |
On Sat, 28 Jun 2014 07:37:41 -0400 |
| 2 |
"Anthony G. Basile" <blueness@g.o> wrote: |
| 3 |
|
| 4 |
|
| 5 |
> > - The way layman handles branches has also changed. |
| 6 |
> > Users will not be able to specify branch via a tag such |
| 7 |
> > as <branch>fubar</branch>, and the branch variable |
| 8 |
> > will now be handled on a per source URL basis. Changes |
| 9 |
> > will be made to the documentation to reflect this change. |
| 10 |
> |
| 11 |
> What does "will now be handled on a per source URL basis" mean |
| 12 |
> exactly? Before documenting this, let's make sure its actually going |
| 13 |
> to be useful to people and embeddable in scripts, etc. Can you give |
| 14 |
> a better description of how layman will be able to select and switch |
| 15 |
> between branches. |
| 16 |
> |
| 17 |
|
| 18 |
instead of one master <branch>foo</branch> setting for the entire xml |
| 19 |
definition. |
| 20 |
|
| 21 |
The branch spec will be an attribute of the source definition |
| 22 |
<source type='git' branch='foo'>git://bar.com/bar.git</source> |
| 23 |
|
| 24 |
this allows for an overlay to have multiple servers/mirrors and the |
| 25 |
overlay to be in different branches of those different server urls. |
| 26 |
|
| 27 |
Branch support for overlays will fixed at one branch only. There will |
| 28 |
be no branch switching within the installed overlay. If you want to |
| 29 |
release different overlays on different branches of a single git repo |
| 30 |
then you will have to have different xml definitions with different |
| 31 |
overlay names, one for each. Essentially for layman each will be a |
| 32 |
different overlay handled individually. |
| 33 |
-- |
| 34 |
Brian Dolbec <dolsen> |
Archives