On Thursday 16 October 2008 03:27:29 Duft Markus wrote:
> Now some package of mine in a local overlay requires bison and flex.
> It's quite hard to get those to build _and_ work on winnt, so I though
> about splitting the bison ebuilds in dev-util/bison and
> dev-libs/bison-runtime (and the same for flex). What do you think about
> this? Before we started using portage at our company I built the
> runtimes only for winnt, so I know this works (for me)...

that doesnt make sense.  there is no separate "bison-runtime" nor "flex-
runtime".  either a package uses bison or it does not, there is no in between.  
same goes for flex.

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to