Re: Set of patches
Russ Allbery wrote:
> Raphael Geissert writes:
>> Russ Allbery wrote:
>
> There isn't a reasonable place to put it in the lab, though. Consider
> the case of a *.changes file for a binary-only build where there's no
> source package and multiple binary packages.
Right.
>
> It's really a third type of "thing," separate from either source or
> binary packages.
*"thing"*
>
>>> Ideally, I'd like to see changes be a fourth type of "package" that can
>
>> Time for me to say "ew" :)
>
> Why? I mean, it's a little odd in sound, but it fits into the Lintian
> architecture really well, I think.
Sure, now I see your point; but calling it a "package" disturbs me.
I just tried to think about a better name but all I can think about
is "file": "binary package file", "source package file",..., "changes
file", "dsc file", "tdeb package file."
> All of the changes data could can be
> passed in via the $info argument as a Lintian::Collect::Changes object,
> so there's no need to do strange things with the lab.
>
Right.
Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net
Reply to: