[BACK]Return to README.patches CVS log [TXT][DIR] Up to [cvs.NetBSD.org] / pkgsrc / x11 / xview-config

File: [cvs.NetBSD.org] / pkgsrc / x11 / xview-config / README.patches (download)

Revision 1.1, Thu Aug 11 05:57:06 2011 UTC (8 years, 6 months ago) by dholland
Branch: MAIN
CVS Tags: pkgsrc-2019Q4-base, pkgsrc-2019Q4, pkgsrc-2019Q3-base, pkgsrc-2019Q3, pkgsrc-2019Q2-base, pkgsrc-2019Q2, pkgsrc-2019Q1-base, pkgsrc-2019Q1, pkgsrc-2018Q4-base, pkgsrc-2018Q4, pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1, pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3, pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-2016Q4-base, pkgsrc-2016Q4, pkgsrc-2016Q3-base, pkgsrc-2016Q3, pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4, pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4, pkgsrc-2012Q3-base, pkgsrc-2012Q3, pkgsrc-2012Q2-base, pkgsrc-2012Q2, pkgsrc-2012Q1-base, pkgsrc-2012Q1, pkgsrc-2011Q4-base, pkgsrc-2011Q4, pkgsrc-2011Q3-base, pkgsrc-2011Q3, HEAD

Add an explanation of what's going on, in case I get hit by a bus.

This package uses per-topic patches, rather than per-file patches.

This means some of the patches patch multiple files, and some files
are patched more than once. The order the patches are applied in
matters, too. If you use mkpatches or regenerate patches naively you
*will* screw things up. Don't.

If you need to rebuild any of the existing patches, until such time as
pkgsrc gets native support for per-topic patches the proper way is to
(1) make extract, (2) touch work/.patch_done, (3) use quilt or
Mercurial's mq extension to push and pop the patches one at a time and
regenerate as necessary. (When done, don't forget to propagate the
updated patches back to the patches directory if necessary before
making clean.)

However, in general you shouldn't need to rebuild the existing
patches; if you have additional changes, in general they should go in
as additional new patches.

The long-term intent is to move these and the large number of
xview-lib and xview-clients patches to distfile patches, or maybe even
to issue a new distfile. However, doing this usefully requires
organization. Per-topic patches aren't critical for xview-config,
because there's only a handful of relatively minor changes; however,
the old way there are 131 patches in xview-lib and 96 in xview-clients
and (particularly in the absence of cvs rename) it's become nearly
impossible to work with them, so sorting and reorganization has to be
done in small steps.

The intent also is for the xview-config patches to be patch-a?-*,
xview-lib patches to be patch-[b-n]?-* or thereabouts, and the
xview-clients patches to be patch-[o-z]?-* or thereabouts, so that the
three sets of patches can be combined later without excessive
difficulty. These three sets should be disjoint: files in config/ are
patched in xview-config, files in clients/ are patched in xview-clients,
and the rest are patched in xview-lib. The build is such that there's
no overlap at build time.

Hopefully the above is enough information for someone to pick this up
if I get hit by a bus.

 - dholland 20110811