On 6/5/06, Andrew Benton <[EMAIL PROTECTED]> wrote:
Randy McMurchy wrote:
> This was done because we should never, ever modify a patch once it has
> been checked into the repository. There is no way folks can know the
> patch has been modified. So, if you keep sources around, especially
> patches, and the book's version of the patch has not been updated, why
> would you download it again?
Perhaps because the patch would not apply? Why would anyone keep a patch
which won't apply cleanly? I only removed a comment that broke the
patch. I left the code intact.
Anything that causes the patch md5sum to change requires a new patch
version. Otherwise someone who has already downloaded the patch before
will not know that the patch in the repository has been updated. If
the upstream package developers started doing that, we would be
screaming at the top of our voice. (I think the popt maintainer did
that and it caused problems for us).
Haven't you got something useful you could be doing?
That is uncalled for.
--
Tushar Teredesai
mailto:[EMAIL PROTECTED]
http://www.linuxfromscratch.org/~tushar/
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
