On Dec 18, 2006, at 7:56 AM, David R. Morrison wrote:
> On Dec 18, 2006, at 7:48 AM, Dave Vasilevsky wrote:
>> On Dec 18, 2006, at 10:28 AM, David R. Morrison wrote:
>>> So we would need a way of archiving info and source files, and
>>> being able to point someone to the precise info and source files
>>> which were used to create the binary. We do this already for the
>>> official bindists, by tagging the source and info files in CVS
>>> and storing a copy of the tagged files in the appropriate
>>> directory tree within the "Archive Browser" http://
>> We can quite easily determine the exact CVS path and revision of
>> the .info/.patch files used for any build. It wouldn't be a bad
>> idea to stuff this information in every deb, maybe in %p/share/doc/
>> %n/fink-info or some such. (Alternatively, it could go into the
>> Description field.) We could also include a direct link to the
>> ViewVC interface for the files in question, eg: http://
> That's a nice idea. While we're at it, we could give URL's to the
> source files in the distfiles, so that there was a single place to
> look to find pointers to all the sources used to create the .deb.
> But I have a question: in rsync updating, don't we throw away the
> CVS directories? How shall we keep the CVS version data available
> to fink at deb-building time?
> Or maybe we just make it a build-time option about whether to
> include this 'pointer-to-the-source' file or not... but that of
> course contravenes the long standing hope that a .deb will be the
> same no matter where it is built.
> -- Dave
Actually, there is a much simpler solution: stuff the .info
and .patch files themselves into the .deb (along with pointers to the
distfiles copy of the source file(s)). This would not increase .deb
size much (except in the case of huge patches, which we discourage in
any case) and is both reliable and easy to implement.