On Tue, May 31, 2005 at 03:20:13PM +0300, Antti-Juhani Kaijanaho wrote:
> A thought:
>
> > Perhaps I'm still missing something?
>
> I'm sure you are aware that Darcs really hates autogenerated files in
> its repositories: configure scripts can easily trigger the infamous very
> bad merge behaviour. On the other hand, Debian packages are encouraged
> to include autotools-generated configure and Makefile.in (etc.) in the
> package in order to avoid the mess that is created by autotools version
> mismatch if they are run at build time.
Hmm. I had usually thought that just the opposite was true; many
debian/rules scripts specifically call auto{conf,make,whatever} so that
they get the latest and greatest behavior for all the arches that Debian
supports. There's no need to keep them in the source package in that
case.
I still think that the correct thing to do is to have debian/rules clean
remove these files so they are not in the Debian source package (even if
they are in the orig.tar.gz), but I will see what I can do in
darcs_load_dirs to ignore boring files. I do see your point there.
> Perhaps darcs is not a good version control system for Debian packages
> after all?
No, I don't think so. I think this is the first time this has ever been
done, so we are all learning as we go.
-- John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
