[p4] How to make a clientspec which syncs only to a given tag

[William Deegan]

I filed an enhancement request with Perforce, They responded that
there is already a request for the feature,but didn't say if it was scheduled
for a particular release.
They requested the use-cases for this feature.

So I suppose if you want this feature best thing to do is to go ahead and
request an enhancement and give the your individual use-cases for this
feature.

-Bill

On 8/23/06, Weintraub, David <david.weintraub at bofasecurities.com> wrote:
> I actually agree with that this should be a feature: Being able to
> specify labels, changelists, dates, etc. It would be nice to also
> specify that a client is also "read only". That way, you could create a
> client for a specific release. It'll map the files, from the depot, and
> download the right versions.
>
> Actually, this is even more important for branch and label specs. I want
> to be able to create the specs, then use the p4 tags, integrate, and
> labelsync without having to specify versions. That way, I can go back to
> the label and branch forms, and see what versions I was labeling and
> branching to.
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of William Deegan
> Sent: Wednesday, August 23, 2006 1:22 PM
> Cc: Perforce Users
> Subject: Re: [p4] How to make a clientspec which syncs only to a given
> tag
>
> I'd still say ideally perforce would allow the clientspec to indicate
> versions of files, including via labels.
>
> Anyone think that's a bad idea, as opposed to itemizing ways to work
> around not having that functionality?
> -Bill
>
> On 8/23/06, Ivey, William <william_ivey at bmc.com> wrote:
> > > it really is the equivalent of two separate clients.
> >
> > Except that I don't need to maintain multiple clients, or worry about
> > which one I am using. (Also, p4win doesn't play well with the P4CONFIG
>
> > files so auto switching isn't useful there - or hasn't been, I don't
> > know if that's been improved lately.)
> >
> > Also, since my client spec has some "quirks" in it, I'd have to make
> > sure those were all properly duplicated. More work than I like.  -Wm
> >
> >
> > > -----Original Message-----
> > > From: Weintraub, David [mailto:david.weintraub at bofasecurities.com]
> > > Sent: Wednesday, August 23, 2006 8:14 AM
> > > To: Ivey, William; Perforce Users
> > > Subject: RE: [p4] How to make a clientspec which syncs only to a
> > > given tag
> > >
> > >
> > > Okay, that's another way of setting yourself up, but, as a forcing
> > > function, it really is the equivalent of two separate clients.
> > >
> > > Imagine that you have two separate clients:
> > >
> > >
> > >     Client: client-branch1
> > >     Root: C:\p4clients\myproj\BRANCH-1
> > >     View:
> > >          //depot/myproj/BRANCH-1/... //client-branch1/...
> > >
> > > And
> > >
> > >     Client: client-branch2
> > >     Root: C:\p4clients\myproj\BRANCH-2
> > >     View:
> > >          //depot/myproj/BRANCH-2/... //client-branch2/...
> > >
> > >
> > > Now, imagine you have a single client for both branches:
> > >
> > >    Client: client-myproj
> > >    Root: C:\p4clients\myproj
> > >    View:
> > >        //depot/myproj/...  //client-myproj/...
> > >
> > > In both situations, to switch from one branch to another requires
> > > you to switch from directory C:\myproj\BRANCH-1 to directory
> > > C:\myproj\BRANCH-2. It is hard to accidentally switch branches
> > > without meaning to. Actually, that's the way we work here. It makes
> > > doing integrations much easier since you have both branches in a
> > > single client.
> > >
> > > -----Original Message-----
> > > From: perforce-user-bounces at perforce.com
> > > [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey,
> > > William
> > > Sent: Tuesday, August 22, 2006 4:07 PM
> > > To: Perforce Users
> > > Subject: Re: [p4] How to make a clientspec which syncs only to a
> > > given tag
> > >
> > > > -----Original Message-----
> > > > From: perforce-user-bounces at perforce.com
> > > > [mailto:perforce-user-bounces at perforce.com]On Behalf Of Weintraub,
>
> > > > David
> > > >
> > > > If I want to change branches, I have to either physically
> > > redefine my
> > > > Perforce client or use another Perforce client.
> > >
> > > Or, none of the above. I work on three or four branches in any given
>
> > > week, usually two during a day, and the only thing I do is cd to a
> > > different directory. My client views contain wild cards so different
>
> > > branches have different corresponding local directories. Local
> > > storage is cheap.
> > >
> > > Or am I missing something?
> > >
> > >  -Wm
> > >
> > >
> > > _______________________________________________
> > > perforce-user mailing list  -  perforce-user at perforce.com
> > > http://maillist.perforce.com/mailman/listinfo/perforce-user
> > >
> > >
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>