Re: dh_python2 and large /usr/share/pyshared
Scott Kitterman <debian@kitterman.com> writes:
>>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.
My case looks exactly like what devref and Lintian write about:
significant amount of architecture-dependent data. The problem of
dependency loops or broken packages is also quite common in this case:
Just by looking through packages that end with "n-data", the first I
found is f.e. "amsn-data" [1], which is only usable with the "amsn"
package, but doesn't have it in its dependency list. The case that the
-data file is really usable independent from the main package seems to
be a rare special case.
I don't see a fundamental difference between this example and my one --
except that amsn-data is 29 MB, any in my case this would be ~4 MB; but
there I would trust the limit that is set in lint.
Since I am still quite a newcomer: what is the problem with dependency
loops, especially as long as they are within the same source package?
Independent of this, my question remains how one would create an
architecture independend subpackage with dh_python2.
Best regards
Ole
--
[1] http://packages.debian.org/squeeze/amsn-data
more examples: gmerlin-data, hugin-data, john-data,
konversation-data, nateon-data, ...
Reply to: