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

[William Deegan]

On 8/23/06, Monica Sanchez <msanchez at freedomscientific.com> wrote:
> I think this may be very useful.
> Example:
> - Clientspecs for old releases.
> - Clientspecs using labels when the same source code is used on
> different projects.
> - Clientspecs defining by a label a third party software directory
> version.
>
>
> I'd also love to have #include, and date-time option on the clientspec,
> one example for this will be that one person can update and test a third
> party software, submit it, label it and modify the "include" file for
> third party software, so all users will start using this latest code for
> this specific vendor.

I'm also thinking of the case where subsystems are "promoted"
separately, so the master
builder can move tags on subsystems as they pass their tests, so developers
can limit the other projects they compile against.

Anyway I think it's worth filing an enhancement request given other revision
control systems support this type of usage, I'd think it wouldn't be too
hard to implement.
-Bill

>
> Thanks,
> Monica
>
>
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey, William
> Sent: Wednesday, August 23, 2006 2:38 PM
> To: Perforce Users
> Subject: [BULK] Re: [p4] How to make a clientspec which syncs only to a
> given tag
> Importance: Low
>
> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com
> > [mailto:perforce-user-bounces at perforce.com]On Behalf Of William Deegan
> >
> > 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
>
> For my own use, I might find it convenient in a couple of cases.
> But to be honest, I might be the only around here who would use it,
> and if some of the others did try to use it, my experience is
> they'd forget it was set inside the client spec and call me to
> diagnose why their setup is "broken".
>
> So, I don't have a strong feeling one way or the other. It's not
> something I miss having, and I'm kind of partial to making the
> actions explicit on the command line rather than hiding them, but
> for those who do find it useful, lobby for it.
>
> -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
>