CODEWITHSUNDEEP
perforce
Will P
Will P

Reputation: 192

Deploying a third party library in perforce

I'm working on a third party integration of some technology into an existing product. Currently I'm contracted to the existing product owners to do this, but we both want to make it clear that my work us an addition to the product. I have access to their perforce server, where a binary deployment of my project lives, but the source code for my work lives in another perforce repository. The client doesn't want to mark my folder as writable on their server, but I regularly update the binary files for local testing. Is there some way I can tell perforce to ignore the directory of my product in the clients repositor, without changing it for everyone on th project?

Upvotes: 0

Views: 69

Answers (1)

Samwise
Samwise

Reputation: 71464

Have the client create a branch of their binaries that's just for your use. They should either make this branch writable by you, or set up some other system whereby they'll "drop" your changes there.

When they're ready to accept your changes, they simply copy them from your branch to their "live" version that everyone else uses.

Upvotes: 2

Related Questions