For the record, I'm in favor of making ICU a requirement for building Parrot, not an optional add-on. Eventually when we realize that seamless built-in unicode support is a core selling point for Parrot, I think we will want to make that change. I'm perfectly happy with making it a dependency for Parrot's package on Debian and anywhere else.
The version of NQP we're shipping with Parrot now is the older NQP-rx. I think we're building it as the "parrot-nqp" binary. This version is used for some things in the core repo and for some older HLLs. The new 6model-powered version is called simply "NQP" and is not shipped with the Parrot repo. Eventually our plan is to eliminate NQP-rx and replace it with the new NQP (maybe even snapshotting it into the Parrot repo), but we aren't there yet. --Andrew Whitworth On Thu, Mar 22, 2012 at 12:10 PM, Allison Randal <[email protected]> wrote: > The Debian Rakudo packagers are requesting that ICU be made a > requirement for the Debian Parrot packages. They're trying to build nqp > from source and it fails tests without ICU. I have a couple of questions > around this: > > - I hate adding extra dependencies, but I also tend to lean toward > supporting whatever languages need from the Parrot packages. Anyone see > any problem with requiring ICU for Parrot on Debian? > > - We're currently shipping a version of NQP pre-built in Parrot. If > people are building nqp from source separately (or just installing it > from packages), can we drop that pre-built version from the Parrot repo? > > Allison > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
