[p4] Re: Perforce Configurations
johan.nilsson at esrange.ssc.se
Mon Mar 21 00:16:46 PST 2005
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Chuck Karish
> Sent: den 19 mars 2005 20:30
> To: Paul Andrei
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Re: Perforce Configurations
> On Fri, 18 Mar 2005 09:20:22 -0500, Paul Andrei
> <pandrei at foliage.com> wrote:
> > In order to completely specify a file/component version in
> > one has to provide its space-time coordinates: the depot
> path is the
> > location (space coordinate) while the revision/change/label is the
> > time coordinate.
> You seem to have fallen prey to the CM fallacy: the notion
> that source control can be implemented by simply selecting
> the appropriate versions of different files or components
> from the ongoing stream of changes.
> For the most part the real world doesn't work that way. The
> idea of making a link to a label breaks down when the release
> represented by the label needs a bug fix and the fix isn't
> appropriate at the head.
Would it make a difference making the symbolic link point to a
dependency release branch instead (e.g.
//depot/common/superlib/rel/1_1/...)? OTOH, that could make updates (bug
fixes) get into your project without you really wanting it (or perhaps
without even being aware of it).
More information about the perforce-user