That's a bit of a contrived example, but I found this bug for a very similar reason to the one I just described. So, I go ahead and enable perl regular expressions, and use lookbehind: Now, I don't want to match the UUID=, as I'm using this in a script. Here's a simple grep to print out all the UUIDS assigned in my fstab: Note that both say that -P enables perl regular expressions.
Busybox grep regular expressions install#
> install it as /usr/bin/pgrep (similar for egrep and fgrep), and let the > the impression that thats what PATH is for. > I looked through Debian Policy, and cant find the reference. > the behaviour of your system based on nothing more than what order your > against Debian Policy, and for good reason, since it completely changes > Installing binaries with conflicting names in /usr/bin and /bin is > Or use perl itself, which is prett perl-compatible. > supports far fewer options (including, for example, GNU longopts, -R, > pcregrep is not an alternative for grep. > Or, "apt-get install pcregrep" if this feature it so important to bin/grep with /usr/bin/grep (I have yet to hear about why this is
So the options are to include libpcre.so in /lib, or replacing The problem, and having grep -P supported?Īs I stated before, pcregrep isnt a serious solution. Rather than discussing fixing the documentation, can we discuss fixing
0 kommentar(er)
