Rather than discussing fixing the documentation, can we discuss fixing the problem, and having grep -P supported?
As I stated before, pcregrep isnt a serious solution. Nor is using perl. So the options are to include libpcre.so in /lib, or replacing /bin/grep with /usr/bin/grep (I have yet to hear about why this is against policy). I'm sure there are other solutions. Anyone? Paul On 5/22/06, Paul <[EMAIL PROTECTED]> wrote: > >> Or, "apt-get install pcregrep" if this feature it so important to > you. > > pcregrep is not an alternative for grep. It is considerably slower, and > supports far fewer options (including, for example, GNU longopts, -R, > --color) > > >> Or use perl itself, which is prett perl-compatible. :) > > lol. Not a serious option for anyone. > > >> Installing binaries with conflicting names in /usr/bin and /bin is > against Debian Policy, and for good reason, since it completely changes > the behaviour of your system based on nothing more than what order your > PATH is in. > > I looked through Debian Policy, and cant find the reference. I was under > the impression that thats what PATH is for. A comprismise could be to > install it as /usr/bin/pgrep (similar for egrep and fgrep), and let the > user symlink it themselves. > > -- > grep -P is not supported > https://launchpad.net/bugs/15051 > -- Paul Biggar [EMAIL PROTECTED] -- grep -P is not supported https://launchpad.net/bugs/15051 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
