Re: How to retrieve a directory tree from perforce.freebsd.org?

On 2007-08-31 20:01, Mel <fbsd.questions@xxxxxxxxxxxxxxxxxxxx> wrote:
On Friday 31 August 2007 19:50:19 Howard Goldstein wrote:
Dang. Like an idiot savant, perforce appears to be (channeling Yoda I
am?) Time for a script to workaround perforce's needlessly overcomplex
stupidity. Thanks for letting me know I'm beating my head against the
wall with the out-of-box tools...binary only at that.

I assume that since sources in perforce is work-in-progress that may
or not become official work-in-progress (-current), download
complexity is a plus.

Not really. It's just the way Perforce works.

Even "work in progress" repositories are interesting things to tinker
with, since testing before something is finalized in an "official"
tree is easier this way :)

Perforce can be used for this sort of 'experimental cross-developer
testing', and its branching, merging and history support is quite fast,
elegant and featureful. It just has a few points which are, to put it
mildly, 'annoying' if you are not used to the way Perforce works.

Having said that, the perforce.freebsd.org server has played an
instrumental role in keeping our CVS tree "clean" from feature-related
branches, and its usefulness to the Project should not be underestimated
just because of its (few) limitations :-)

_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Public Access to Perforce?
    ... > access to the perforce server. ... The netperf work is exported as regular patch sets on the ... this has been done using separate work areas, often based on separate CVS ... I think you're arguing that parallelism and branching are OK as long as ...
    (freebsd-current)
  • Re: FreeBSD moves to Subversion
    ... FreeBSD `src/' is the matter. ... branching that Perforce has in $. ... branching isn't used in CVS for the Perforce projects is that it's so ...
    (comp.unix.bsd.freebsd.misc)