Re: suffix for packages with (optional?) Python extensions

[Yaroslav Halchenko <debian@onerussian.com>]

On Mon, 16 Jul 2012, Scott Kitterman wrote:
> >> 1.  python{3}-foo which is arch all and follows the current naming
> >convention 
> >> of foo being the name you import.  It would depend on the arch any
> >python-foo-
> >> ext package.

> >all -> any package dependencies are often icky, if you want them to be
> >strictly versioned.  Probably not a showstopper, but something to be
> >aware of.

> Right now I'd just like to understand what is being proposed.

look at any of mine python-* packages having corresponding -lib package.
e.g.

$> apt-get source python-nipy
...
$> grep -e Package: -e Architecture:  nipy-0.2.0\~rc2+git27-g7b9b5a5/debian/control        
Package: python-nipy
Architecture: all
Package: python-nipy-lib
Architecture: any
Package: python-nipy-lib-dbg
Architecture: any
Package: python-nipy-doc
Architecture: all


-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik