[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #5 from Justin Zobel --- Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 --- Comment #4 from Massimo Burcheri --- I had some old clients from 2007 that did not need P4CONFIG to be set, and the current from 2017 doesn't either. afaik the default always was to configure all in the environment: P4LOC P4CLIENT P4PORT P4USER Having a P4CONFIG and some file found this can overwrite these settings while superseeding with parent directories $P4CONFIG. So p4 on some /workspace/file would be different if your $PWD is $HOME or /workspace/file as that $P4CONFIG there could switch your $P4CLIENT. It could even switch your server $P4PORT. It's more a git way but we don't use it as things get more obfuscated by this. Anyway the perforce plugin should not rely on it. p4 will use the feature if configured. You could better add some local environment settings to set P4CLIENT per KDevelop project or just inherit the system environment. Look at qtcreator, they have some P4CLIENT and P4PORT settings in the dialog replacing the system environment settings. Usually on shell we switch the "project" by scripts exporting P4CLIENT to a subshell. While working in KDevelop don't have that option anymore so I would need to set these per project, but could also be done by the project generic environment settings of KDevelop. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 --- Comment #3 from Morten Danielsen Volden --- (In reply to Massimo Burcheri from comment #2) > Having P4CONFIG unset is a valid P4 environment. True. IIRC, older p4 clients needs the P4CONFIG to be set - no? Also. If you P4 environment does not rely on the P4Config to be set what does it rely on to e.g. read the server address for a specific project? -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 --- Comment #2 from Massimo Burcheri --- Having P4CONFIG unset is a valid P4 environment. But the perforce plugin refuses to load. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 --- Comment #1 from Morten Danielsen Volden --- P4CONFIG only points to the filename that the plugin should search a given directory structure for. So if you have a project folder structure like this: MyCoolProject Foo Bar Baz Then you would only need to place your .p4config (or whatever you choose to call it) in the top-level directory of your project (Like Git and Hg.) -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 376789] Drop P4CONFIG check
https://bugs.kde.org/show_bug.cgi?id=376789 Kevin Funk changed: What|Removed |Added CC||mvold...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
