Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-pcre
Version : 0.7
Upstream Author : Name
* URL : https://github.com/awahlig/python-pcre
* License : BSD-3
Programming Lang: Python, C
between PCRE, Emacs and rx regexp
syntax
This package provides `pcre2el' or `rxt' (RegeXp Translator or RegeXp
Tools), a utility for working with regular expressions in Emacs,
based on a recursive-descent parser for regexp syntax. In addition to
converting (a subset of) PCRE syntax into
On Fri, Nov 20, 2015 at 10:24:09AM +, Jonathan Dowland wrote:
> Is there anything preventing a rename of libpcre2-dev to libpcre-dev, first?
That should, of course, have been
"Is there anything preventing a rename of libpcre3-dev to libpcre-dev, first?"
On Wed, Oct 28, 2015 at 03:51:26PM +, Matthew Vernon wrote:
> No, the -dev packages will need to be co-installable, too. I expect
> we'll need to ship PCRE (including its -dev package) for quite some time.
>
> ...so I'm still not sure what to call PCRE2 :-/
Sorry i
On 10/22/2015 10:47 AM, Matthew Vernon wrote:
The natural thing to call the PCRE2 packages is pcre2, but that's going
to lead to confusion - ISTM that something that makes it clear that
PCRE2 is newer than PCRE is desirable. And, obviously, PCRE & PCRE2 need
to be co-installable.
Matthew Vernon writes:
> No, the -dev packages will need to be co-installable, too. I expect
> we'll need to ship PCRE (including its -dev package) for quite some time.
> ...so I'm still not sure what to call PCRE2 :-/
It's pretty ugly, but I'd tend to use libp
Hi,
Simon Richter writes:
> Hi Matthew,
>
> On 22.10.2015 16:47, Matthew Vernon wrote:
>
> > Upstream has a new PCRE library, which they hope everyone will
> > eventually migrate to, which is called PCRE2. It is currently version
> > 10.20. It ships things named
Hi Matthew,
On 22.10.2015 16:47, Matthew Vernon wrote:
> Upstream has a new PCRE library, which they hope everyone will
> eventually migrate to, which is called PCRE2. It is currently version
> 10.20. It ships things named like libpcre2-8.so.0, and its pcregrep is
> called pcre
Hi,
PCRE has been in Debian for some time; the current packages correspond
to upstream 8.35 (with a pile of backported security fixes, which I hope
will end up as an 8.38 release some time soon). These packages are
called pcre3 (and libpcre3 ships libpcre.so.3).
Upstream has a new PCRE library
Quoting Steve Langasek ([EMAIL PROTECTED]):
> > > Description : a lightweight GHC library for Perl 5 compatible
> > > regular expressions
>
> > Being lecc cryptic would help, here.
>
> > I suggest expanding "GHC" if possible, at the expense of "Perl 5"
> > "lightweight" and/or "compatible
On Sun, Feb 10, 2008 at 06:43:59AM +0100, Christian Perrier wrote:
> Quoting Recai Oktaş ([EMAIL PROTECTED]):
> > Package: wnpp
> > Severity: wishlist
> > Owner: "Recai Oktaş" <[EMAIL PROTECTED]>
> >
> > * Package name: pcre-light
> >
Quoting Recai Oktaş ([EMAIL PROTECTED]):
> Package: wnpp
> Severity: wishlist
> Owner: "Recai Oktaş" <[EMAIL PROTECTED]>
>
> * Package name: pcre-light
> Version : 0.3.1
> Upstream Author : Don Stewart <[EMAIL PROTECTED]>
> * URL
Package: wnpp
Severity: wishlist
Owner: "Recai Oktaş" <[EMAIL PROTECTED]>
* Package name: pcre-light
Version : 0.3.1
Upstream Author : Don Stewart <[EMAIL PROTECTED]>
* URL : http://www.example.org/
* License : BSD
Programming Lang:
On Thu, Jun 19, 2003 at 09:10:21AM +0100, Philip Hazel wrote:
> Thanks, problem noted. I'll do something when I next work on PCRE, but
> that won't be for a while.
Mark, could you look for a fix in the debian version?
Otherwise I can have a look at it ...
Cheers.
--
St
On Thu, 19 Jun 2003, Mark Baker wrote:
> Philip, I have CC'd you on this mail as the upstream author, because I
> believe this counts as a bug in pcre. I would suggest as a minimum
> removing the printing of the study size from the test.
Thanks, problem noted. I'll do somethi
nd sid (gcc 3.2.something).
The tests for pcre consist of running a test program, and then comparing
its output against an expected output. One thing that the program does
is the following:
new_info(re, extra, PCRE_INFO_STUDYSIZE, &size);
[...]
fprintf(outfile, "S
I've just uploaded version 3 of libpcre.
I've put it in a new package, libpcre3, and given it a new soname. I'm not
sure if this was strictly necessary or not: the upstream documentation
doesn't mention binary compatibility with the old version, probably because
older versions weren't intended to
17 matches
Mail list logo
