| 1 |
On Wed, 7 Dec 2016 10:16:47 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
> > Basically you're suggesting to drop either of those modes. Now I'm |
| 4 |
> > asking, would one of those (likely tinfo mode) be workable in all |
| 5 |
> > packages? Do you find that it would cause less issues than this |
| 6 |
> > solution? And I'm talking about end-user issues, not ebuild |
| 7 |
> > implementation issues. |
| 8 |
> |
| 9 |
> Yes. If I recall correctly, libncurses links to libtinfo, so packages |
| 10 |
> already built continue to work. Of course, new packages (including |
| 11 |
> deps of the libraries already linked to libncurses) may fail to build. |
| 12 |
|
| 13 |
|
| 14 |
So ncurses -> ncurses[tinfo] is not breaking. |
| 15 |
ncurses[tinfo] -> ncurses breaks ABI all apart. |
| 16 |
|
| 17 |
Still a bad idea to have this randomly switchable. |
| 18 |
|
| 19 |
Having the useflag around is not wrong, but we should definitely force |
| 20 |
one state by pacakge.use.mask/force. People that want to experiment |
| 21 |
should know what they're doing. Remember libcxx on fbsd, right ? |
| 22 |
|
| 23 |
|
| 24 |
Alexis. |
Archives