| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
If we go there, we will need to transition equery from where it is to the new |
| 5 |
stable interface through a path of functional deprecation notices. We should |
| 6 |
have a plan. |
| 7 |
|
| 8 |
I also think before any collaborative refactoring gets underway we need more |
| 9 |
consensus than we have now. I think we need a formal declaration of what an |
| 10 |
equery tool (module?) should do (abstract methods), and naming conventions for |
| 11 |
the tools that hopefully make it hard for them to overlap too much. |
| 12 |
|
| 13 |
- -Michael |
| 14 |
|
| 15 |
Douglas Anderson wrote: |
| 16 |
| That's an awful lot of "searching" there for something that's |
| 17 |
| definitely not a search. List is really ambiguous, but whatever. |
| 18 |
| |
| 19 |
| I understand the point of having a stable interface, but this is |
| 20 |
| probably the most widely recommended tool on the forums and #gentoo. |
| 21 |
| Stability is not a good enough reason to let it bit rot. Wasn't a more |
| 22 |
| unified tool interface also one of the original goals of gentoolkit? |
| 23 |
| |
| 24 |
| -Doug |
| 25 |
| |
| 26 |
| |
| 27 |
|
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 30 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 31 |
|
| 32 |
iEYEARECAAYFAkk7eEUACgkQzwtr5yY0JZyfzQCdHBJWQvgbiZUqx0p32OdE+bgU |
| 33 |
hYQAnjLfd05eUgpVrqZEB8Jam4qyLl5z |
| 34 |
=zSKs |
| 35 |
-----END PGP SIGNATURE----- |
Archives