Re: [Hampshire] Re: Application installers

>> So it's no longer pristine. You've lost some traceability.
>
> Er, it's a filename change. Run md5sum on it if you care.

OK, you get a source package called libfoofs. It contains a source
libfoofs<something>.orig.tgz. The md5sum is
e6956c130f29d0099291281dc99f049b. What is it?

There's an amount of hunting down to be done with that; if the tarball had
kept its original name, that would not have been necessary. And, as far as
I can tell, the only reason for changing its name is that the Debian
Policy Manual tells you to. I maintain that it would make far more sense
to rescind that rule - particularly since the .dsc file that describes the
source package lists its components anyway.

> spec + patches, but now you are asking your repositories to store both
> the srpm and the split-up srpm.

No I'm not - I'm merely mentioning that many (not all) repositories hold
both full-fat SRPMs and the spec files that were used to create them.

The patch files are of little real use unless you're starting from the
same original tarball - in which case, you want the whole SRPM.

Vic.