Re: Moving pkgsrc-wip away from SourceForge

[Robert Elz <kre%munnari.OZ.AU@localhost>]

    Date:        Sat, 04 Jul 2015 12:21:21 -0400
    From:        Greg Troxel <gdt%ir.bbn.com@localhost>
    Message-ID:  <rmiio9z6ghq.fsf%fnord.ir.bbn.com@localhost>

  | Benny Siegert <bsiegert%gmail.com@localhost> writes:
  | > a) moving away from sourceforge is a good occasion for moving away from CVS,
  | 
  | agreed

I disagree - unless the plan is also to move pkgsrc away from cvs (at the
same time.)

The two ought to be using the same technology throughout, or part of the
rationale for wip to exist is lost.

I know that I unpack wip (when I use it) into .../pkgsrc/wip and then
use
	cd .../pkgsrc; cvs up

to update both pkgsrc and pkgsrc/wip in one operation.   That makes wip behave
and act, just like pkgsrc, and I can (once it is set up) simply forget that
it is a little different.

While wip serves to develop packages, for which the version control tool is
irrelevant, it also serves to teach people how to operate on pkgsrc, which
requires that the two use the same mechanisms.

kre