| 1 |
On Thursday 16 October 2008 03:27:29 Duft Markus wrote: |
| 2 |
> Now some package of mine in a local overlay requires bison and flex. |
| 3 |
> It's quite hard to get those to build _and_ work on winnt, so I though |
| 4 |
> about splitting the bison ebuilds in dev-util/bison and |
| 5 |
> dev-libs/bison-runtime (and the same for flex). What do you think about |
| 6 |
> this? Before we started using portage at our company I built the |
| 7 |
> runtimes only for winnt, so I know this works (for me)... |
| 8 |
|
| 9 |
that doesnt make sense. there is no separate "bison-runtime" nor "flex- |
| 10 |
runtime". either a package uses bison or it does not, there is no in between. |
| 11 |
same goes for flex. |
| 12 |
-mike |
Archives