In Perforce, is there a way to mark that a file should never be integrated?

In our Perforce workspaces at work, there are a couple of control files that contain branch information that should never be integrated acr开发者_C百科oss branches.

Is there a way to tell Perforce to always ignore these files in integrations?

---

You could set up a branch spec and use that for your integrations.

---

You may be able to use some type of permissions through p4 protect, so that only the admin can modify them. I know this works for actually checking out and checking in a file, but I'm not sure about integrating it to another branch.

---

You could write a server-side trigger script that looks for the control file names and filters them out of an integrate.

There's pretty good documentation on triggers. There's a load of examples too in the public Perforce depot.