| 1 |
On 10/20/2015 03:34 AM, Alexander Berntsen wrote: |
| 2 |
> On 15/10/15 19:42, Paul Varner wrote: |
| 3 |
> > Over the last couple of days, I have done the following: |
| 4 |
> |
| 5 |
> > 1. Migrated the gentoolkit-dev branch to its own gentoolkit-dev.git |
| 6 |
> > repository |
| 7 |
> > 2. Moved the gentoolkit branch to master on the |
| 8 |
> > gentoolkit.git repository |
| 9 |
> Why did you not just make gentoolkit master, and leave gentoolkit-dev as |
| 10 |
> a branch? That's certainly the common way of using git. |
| 11 |
> |
| 12 |
|
| 13 |
Mainly, because at this point gentoolkit and gentoolkit-dev are now |
| 14 |
almost completely separate code bases as well as being separate packages. |
| 15 |
|
| 16 |
They share a common ancestry and that can be seen looking through the |
| 17 |
commit log, but starting with gentoolkit-0.2.5, gentoolkit started |
| 18 |
migrating to python as the only scripting language and utilizing the |
| 19 |
Portage API with setuptools as the build system. The two remaining bash |
| 20 |
scripts are being rewritten in python and when that is complete, they |
| 21 |
will be completely separate code bases. |
| 22 |
|
| 23 |
gentoolkit-dev has stayed as a collection of stand-alone scripts written |
| 24 |
in multiple languages intended mainly for Gentoo developers. |
| 25 |
|
| 26 |
Since they really do not share any code anymore, it did not make sense |
| 27 |
to me keeping gentoolkit-dev as a branch and it should be in its own |
| 28 |
repository. |
| 29 |
|
| 30 |
Regards, |
| 31 |
Paul |
| 32 |
. |
Archives