Re: getting rid of the .changes requirements
Peter Palfrader <weasel@debian.org> writes:
> The utility - having nice mails on the -changes list - does not justify
> the cost - it's quite painful, sometimes non-trivial, and simply
> annoying work to get your build environment to produce .changes file
> that meet this requirement.
Could you describe how it is painful or non-trivial? It isn't that I
disagree with you, I just simply do not see it because it is quite easy
for me to do and I'm curious to know in what situations that is difficult.
Reply to: