[Pkg-Cyrus-imapd-Debian-devel] .orig.tar.gz orig vs. repacked

Henrique de Moraes Holschuh hmh at debian.org
Mon Aug 1 20:18:01 UTC 2005


On Mon, 01 Aug 2005, Sven Mueller wrote:
> handle all those files I removed when original creating the repacked
> tarball? I removed many which are unused (including various empty

The cyrus21 packages have a debian/removable.files (or somesuch) logic, also
in autogen.sh, to build such a list of "blow them away" files that are rm
-f'ed at debian/rules clean time.

> the config.guess and config.sub file. But how do we handle the files
> which get rebuilt automatically? If we want to keep our diff as small as

*ALL* files that are automatically generated *are* to be cleaned up (i.e.
removed) by debian/rules clean IMHO.  Anything else is just a major pain for
no good reason.

Do it, and the world suddenly becomes a nicer place, and the .diffs smaller
:)

And we can make dpatch work with a pos-debian/rules-clean tree, to keep our
sanity while at it.

> need to create backups of those files during configuration (respectively
> patch) time and restore them during cleanup (resp. unpatch) time. But
> there are quite some such files, so this task isn't too easy IMHO.

Why? If they are auto-generated, blow them away to hell, and regenerate them
during the build, using proper Debian-packaged stuff which is probably far
less buggy than whatever CMU is using (I speak from experience).

Heck, my standard way to deal with CMU's crap of a et/ dir and makefiles
which always screw up the build by using that outdated PoS instead of
Debian's perfectly fine and up-to-date et stuff is to rm -rf et/ at
debian/rules clean... :)

> PS: Any ontakers? I won't have time to do anything on the cyrus22
> project for the next two or three weeks as far as I can tell now.
> PPS: BTW: Henrique, you said you would work on cyrus22 during DebConf. I
> assume you didn't find the time to do so, just like me?

I did work, but not much.  The major unstable breakage killed any
possibility of doing builds for a while, and my dev machine is back into
track for 3 or 4 days only, now :P

I should get back to cyrus, commit the doc work I did already (nothing
major), and go right into the clean-the-package-build stuff soon.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh



More information about the Pkg-Cyrus-imapd-Debian-devel mailing list