| 1 |
Not-Forking addresses the upstream vendoring/forking issue, as per the diagrams and explanation |
| 2 |
at https://lumosql.org/src/not-forking : |
| 3 |
|
| 4 |
> Not-forking avoids duplicating the source code of one project within another project, where the projects |
| 5 |
> are external to each other. This is something that is not handled by version control systems such |
| 6 |
> as Fossil, Git, or GitHub. |
| 7 |
> |
| 8 |
> Not-forking avoids project-level forking by largely automating change management in ways that a version control system cannot. |
| 9 |
|
| 10 |
Not-Forking has an ebuild, but not a maintainer. I figured this is the place to mention it. |
| 11 |
|
| 12 |
Best |
| 13 |
|
| 14 |
-- |
| 15 |
Dan Shearer |
| 16 |
dan@×××××××.org |
Archives