| 1 |
Michał Górny posted on Sat, 18 Nov 2017 10:22:34 +0100 as excerpted: |
| 2 |
|
| 3 |
> Introduce a new, more flexible override API in git-r3, in replacement of |
| 4 |
> the LIVE_* API that was pretty much a legacy of git-2. This means to |
| 5 |
> solve the two major limitations of the old API: |
| 6 |
> |
| 7 |
> 1. The variables were based on package names without categories. |
| 8 |
> Therefore, they weren't suitable whenever two packages had the same |
| 9 |
> category. This is quite common when dealing with various programming |
| 10 |
> language bindings/reimplementations, and we can't really rely on every |
| 11 |
> new programming language inventing its own VCS. |
| 12 |
|
| 13 |
I always used package.env in any case, and always wished for a non- |
| 14 |
package-unique env var name variant to make it easier to simply clone the |
| 15 |
file and stuff the commit var as appropriate, instead of having to setup |
| 16 |
the file and fix up BOTH the var name and its value, when I needed to |
| 17 |
bisect a package the first time. |
| 18 |
|
| 19 |
So a variant without the repo OR package name would be my wish, here. |
| 20 |
|
| 21 |
> 2. The overrides weren't suitable for packages checking out multiple |
| 22 |
> repositories (LLVM, wine, glibc). |
| 23 |
|
| 24 |
Valid point there! |
| 25 |
|
| 26 |
-- |
| 27 |
Duncan - List replies preferred. No HTML msgs. |
| 28 |
"Every nonfree program has a lord, a master -- |
| 29 |
and if you use the program, he is your master." Richard Stallman |
Archives