Re: dh_python2 and large /usr/share/pyshared
On Tue, 10 Jul 2012, Scott Kitterman wrote:
> >>>I: python-astropy: arch-dep-package-has-big-usr-share 4137kB 87%
> >>> How do I create an arch independend package that contains these
> >files?
> >> [...] I'd rather not do that. You will likely end up with either
> >> dependency loop or a package that is not useful for anything when
> >> installed alone.
> >Debian Developer's Reference section 6.7.5 (Architecture-independent
> >data) recommends to do so, and I would just trust Lintian's
> >recommendation here.
> >Or are they outdated with todays disk capacities?
> Neither devref nor Lintian are suicide pacts. It's good general advice, but not to the point of creating dependency loops or broken packages.
since our works were mentioned ;) -- yes, we generally split out python
extensions (and anything else arch-dep) into python-*-lib packages
primarily to minimize impact on the archive where we could achieve that
-- we have a dozen of ports, so any MB makes ten-fold impact (and then
do not forget snapshot.d.o).
To overcome any dependency loop, arch:all depends on arch:any -lib and
"broken packages" indeed could happen with annoying one when
arch:any is installed without arch:all package. Then module is
'visible' since all the paths leading there present but most probably
would not be importable/usable. It is easily resolvable (through
installation of the corresponding arch:all package) and I rarely hear
about it this from users. That is why I keep following this scheme for
any new package of such kind despite that it requires a bit of ad-hoc
actions in debian/rules.
Hope this of some help ;-)
--
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
Reply to: