This tells BND what packages should be imported from other OSGi bundles in the OSGi container. In this case, both lines use wildcards in the package name, which means BND will replace these lines with any package used by the exported and private packages that match the prefix. For example, the `scalaz.stream` package uses `scala.math` and hence, BND will generate an import-package statement for that package due to line 42 matching.

Lines 42 and 43 each use the BND `range` macro to adjust the version range used when importing matching packages. BND defaults to the version range `[x.y.0,x+1.0.0)`. Without a custom version range on the scala imports, the dependency on `scala.math` package would be `[2.10,3)`. Because Scala only guarantees binary compatibility on increments of the third version component, we need the version range `[2.10.2,2.11)`. The BND `range` macro lets us generate a string of that form using the template `[===,=+)` and applying the version of the package it is generating the import for (`$<@>`).

The same reasoning applies for the scalaz packages because it uses the same versioning scheme (e.g., 7.0.x are all binary compatible but 7.1.x is not).

For more information on BND and versioning policies, see: http://www.aqute.biz/Bnd/Versioning