On Thu, Oct 05, 2000 at 09:05:23PM -0400, Johnny C. Lam wrote:
: Frederick Bruckman <fb@enteract.com> writes:
: > On Thu, 5 Oct 2000, David Brownlee wrote:
: 
: 	I've had the opposite experience.  I've found it quite
: annoying to track down which patches need to be updated, added, or
: removed.  To some extent, pkgdiff helps, but I find it's much simpler
: to generate one big patch.
: 
: 	It should also be noted that having all the patches in one big
: file makes having a flattened the pkgsrc directory structure have only
: one file per package called patch versus, for some packages, 50+ files
: called patch-aa, patch-ab, ... , patch-by, patch-bz.

We may want to look at taking a page out of OpenBSD's book and think
about having all new ports use names like "patch-foo," "patch-bar,"
(where foo/bar are the names of the files or particular functions that
they patch).

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 302.593.4322               ||  matter of life or death...
email: alexandr@eecis.udel.edu    ||  ...It's much more important
                                  ||  than that!