Re: duplicate library code in a package
- To: email@example.com
- Subject: Re: duplicate library code in a package
- From: Joey Hess <firstname.lastname@example.org>
- Date: Fri, 30 Sep 2005 23:17:57 -0400
- Message-id: <20051001031757.GA578@kitenet.net>
- In-reply-to: <433ADFBA.email@example.com>
- References: <20050928161512.GA1394@sorrow.no-ip.org> <Pine.LNX.firstname.lastname@example.org> <20050928173602.GM11117@miami.familiasanchez.net> <email@example.com> <433ADFBA.firstname.lastname@example.org>
Andreas Fester wrote:
> not necessarily. It must be the original, but it must not be pristine.
That's self-contradictory. And wrong.
> One reason could be to remove autotools dependencies, another could be
> to remove files which would otherwise be removed by the "clean" target
> and would end up in a huge diff.gz.
If you remove files in the clean target they will not appear in your
diff.gz. The clean target is run before generating the diff.
see shy jo
Description: Digital signature