Re: How much data load is acceptable in debian/ dir and upstream (Was: edtsurf_0.2009-7_amd64.changes REJECTED)
Hello,
On 2020-09-14 22:04, Andreas Tille wrote:
> in the Debian Med team there are two GSoC students very busy to write
> autopkgtests for (in the long run) all our packages (if possible).
Very grateful for their effort!
[snip]
> On Sun Sep 13 18:00:08 BST 2020, Thorsten Alteholz wrote:[3]
>> If you really need those data please create a separate source package
>
> That's the question that I'm repeatedly wondering about and thats why I
> assemble all these three rejects here in one mail: What is the general
> opinion for creating a separate source package in cases like this. I
> do not see any profit from an extra source package. From my point of
> view autopkgtest data are belonging to the packaging code and thus are
> fine here. But for sure I might be wrong and would like to clarify
> this hereby.
What about packaging well-known (reference?) datasets to be used in such
autopkgtests (and potentially elsewhere)? If we manage (I mean
copyright-wise) to package some reference datasets, these could be
reused in autopkgtests/examples of great numbers of packages. For
example, a mouse genome could be reused by most of the tools for
subsequence matching, gene/intron region lookup, just to name a few. And
if a package needs that data in some other format, we can always use
converters abundant in Debian.
[snip]
> [1] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-September/084428.html
> [2] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-September/084430.html
> [2a] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-September/084441.html
> [3] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-September/084432.html
Best,
Andrius
Reply to: