Jump to content


Marcurion

Member Since 20 Apr 2019
Offline Last Active Apr 23 2019 06:46 PM
-----

Posts I've Made

In Topic: Is Perforce the right choice for my workflow?

23 April 2019 - 05:21 PM

View PostSambwise, on 23 April 2019 - 04:56 PM, said:

In other words:

p4 integrate //Producer1/main/Assets/_Export/... //Consumer1/main/Assets/_Import/Producer1/...

or whatever reflects what you want to import and where you want to import it to.  Make the copy in the depot rather than remapping it in the client.  You can "integrate" from any path to any other path so there are no limitations whatsoever on how many copies of each folder you make, going between projects, etc.


Thanks a lot again, I get it now :)
Will try around with all your tips for the next few weeks ^_^

In Topic: Is Perforce the right choice for my workflow?

23 April 2019 - 04:06 PM

Hi Sambwise,

thank you so much for your extensive answer, it gives me hope to keep going and trying with Perforce :)

Could you elaborate a bit more on "branching the dependencies into their own namespace" or maybe direct me to a documentation page, tutorial or example?

Also I found this example on Component Based Development (CBD) with Perforce sounds very similar to what I am trying to achieve, but could not try it out yet since I dont have access to a Linux system currently. What do you think?
https://swarm.worksh...ce-software-cbd


Kind reagrds,
Marc