| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Chris White wrote: |
| 5 |
> 1) Create aliases to the new functions, then at some |
| 6 |
> yet-to-be-determined point, kill the aliases and bomb on the scripts |
| 7 |
> (this suffers from procrastination). |
| 8 |
> |
| 9 |
> 2) Make an official release with the new function names and no aliases, |
| 10 |
> as well as the soon to come docs. I sort of like this method because |
| 11 |
> those with official portage tools can adjust their scripts, and simply |
| 12 |
> alter the depend atoms for >= (new API versions) and <= (old versions), |
| 13 |
> effectively forcing/preventing upgrades. |
| 14 |
|
| 15 |
I vote for #1 because it's smoother and easier (which is good for me especially because I do releases). The disruptive change proposed in #2 seems like it would cause unnecessary problems with no practical advantage over #1. |
| 16 |
|
| 17 |
Zac |
| 18 |
-----BEGIN PGP SIGNATURE----- |
| 19 |
Version: GnuPG v1.4.4 (GNU/Linux) |
| 20 |
|
| 21 |
iD8DBQFEwrPM/ejvha5XGaMRAjSNAJ9LURidl/v7MpukPFJyNKUot1qy9ACgznev |
| 22 |
td1QnRm0wxau2Ipo9v23anY= |
| 23 |
=TDgt |
| 24 |
-----END PGP SIGNATURE----- |
| 25 |
-- |
| 26 |
gentoo-portage-dev@g.o mailing list |
Archives