https://github.com/haxpor/p4u
Fill the gap of what missing in p4.
https://github.com/haxpor/p4u
cli command-line p4 perforce
Last synced: 2 months ago
JSON representation
Fill the gap of what missing in p4.
- Host: GitHub
- URL: https://github.com/haxpor/p4u
- Owner: haxpor
- Created: 2020-11-19T04:30:40.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2021-08-03T13:09:59.000Z (almost 5 years ago)
- Last Synced: 2025-01-20T07:35:25.225Z (over 1 year ago)
- Topics: cli, command-line, p4, perforce
- Language: Shell
- Homepage:
- Size: 23.4 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# p4u p4 utility (p4u) to fill up the gap of p4 itself.
It is based on bash script thus working with bunch of shell commands. It works
on top of `p4` binary as released officially but filled the gap for features and
things that could be better.
> For someone coming from `git` to use perforce via its cli 'p4', I bet you know
> what was missing in the latter.
# Installation
You can just clone this repository, then symblink `p4u` file into your executable
path e.g. `/usr/local/bin/`, or you can copy the file there.
To make a symlink from `p4u` to `/usr/local/bin/p4u`, you can execute the following
command
```
ln -s `pwd`/p4u /usr/local/bin/p4u
```
assume that you are currently at the project directory, and you have permission
to create a file at target directory. Otherwise, you might need `sudo`.
# Configuration
Configuration is configured through environment variables for now, until there
would be much more settings to be made, we might change the way to do this.
Set the following environment variables through your aliased or profile file
e.g. `~/.bash_aliases` or `~/.bash_profile`; for example `export
=`
* `P4U_BIN` - to change which `p4` binary to use inside the script
It is a high chance that you would be working on WSL 1/2 with perforce. The
project should be able to built on Windows platform, and able to interact with
command line on WSL. `p4` binary for WSL won't work as it cannot adapt to use
the correct path for each platform correctly. So using `p4.exe` which is a
binary for Windows version, but we execute it on WSL is the solution as it
understands Windows path correctly. Thus it becomes this setting. Most likely,
just set `P4U_BIN=p4.exe` should be fine for WSL environment.
# Features
## `p4u describe`
Original `p4 describe` has limitation as follows
* It doesn't show (additional) diff of newly added files on the shelved
changelist.
* It outputs in non-unified (non-git compatible) format, it needs a particular
flags to make it output just that
* It outputs excessed header text although it's good, but sometimes we want to
directly pipe it to ` ... | view -` (`vim`) to see as diff format immediatley
without manual removal of such header lines.
Usages as implemented
* `p4u describe -S=123456`
* `p4u describe -S=123456 --no-header`
# License MIT, Wasin Thonkaew