https://bugs.kde.org/show_bug.cgi?id=376789
Bug ID: 376789
Summary: Drop P4CONFIG check
Product: kdevplatform
Version: 5.0.80
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: perforce
Assignee: kdevelop-bugs-n...@kde.org
Reporter: massimo.burch...@gmx.de
Target Milestone: ---
Please don't rely on P4CONFIG.
We never used that before, I just learned about that variable after debug
output of KDevelop mentioned that the plugin was not enabled due to missing
P4CONFIG.
P4 works also without P4CONFIG and so should the plugin.
There are 2 pitfalls:
* The plugin was not loaded if the variable isn't set
* Files on my project don't have the perforce context menu
The latter I was able to fix. I had a P4CONFIG=.p4config and some .p4config in
my $HOME seting P4CLIENT. After leaving home and going to /workspace the
context menu disappeared. I learned the P4CONFIG only applies to the current
folder. This can be powerful but confusing. Got that fixed by moving the
.p4config to the parent directory /workspace, but would prefer to not use a
$PWD related configuration.
I know git and hg are doing that as well, but there every clone has the
metadata on top, while things would be more confusing when submitting a
.p4config to Perforce, chicken-and-egg problem.
--
You are receiving this mail because:
You are watching all bug changes.
