Re: cvs-inject vs. orig.tar.gz
From: Steve Greenland <email@example.com>
Subject: cvs-inject vs. orig.tar.gz
Date: Fri, 28 May 1999 15:17:11 -0500
> I finally got around to put the cron package under cvs, using the
> modified cvs-inject that took previous releases and added them to cvs.
> The only problem is that when it created the vendor branch, it used the
> the current date, rather than the file dates, which means that the new
> .orig.tar.gz file created by cvs-buildpackage no longer matches the
> original .tar.gz file. Likewise, the md5sum is different.
I am a beginner of cvs and may not fully understand your question
but I have maintained several packages for Debian JP under cvs.
If your question concerns the difference between the original
package.orig.tar.gz and the one created by cvs-buildpackage
then I do as follows.
Perhaps you will set directory for cvs-buildpackage (conf_rootdir ?).
Let it be /usr/local/src/Packages
Keep the original package.orig.tar.gz somewhere, say
Then in /usr/local/src/Packages/package do
"ln -s /home/john/package.orig.tar.gz ."
In some working directory, you do cvs-buildpackage then
it uses original package.orig.tar.gz in /usr/local/src/Packages/package
instead of creating new package.orig.tar.gz
Of course you can "cp" or "mv" /home/john/package.orig.tar.gz
to /usr/local/src/Packages/package instead of "ln -s"
I do not know this is wright or not but it works fine for me.
If I misunderstand your question do not blame on me, I am
a Japanese and not good at Enaglish :)
Thanks in advance, 1999.5.29
Debian JP Developer - much more I18N of Debian
Atsuhito Kohda <firstname.lastname@example.org>
Department of Math., Tokushima Univ.