On Apr 18, 2009, at 1:24 PM, Ralf S. Engelschall wrote:
On Mon, Apr 13, 2009, Ralf S. Engelschall wrote:
On Mon, Apr 13, 2009, Michael Jennings wrote:
[...]
Yes, the XZ, PCRE and Syck were added to RPM 5.1 recently but a
corresponding entry in the top-level Makefile.am's EXTRA_DIST was
On Apr 15, 2009, at 7:52 AM, Ralf S. Engelschall wrote:
On Tue, Apr 14, 2009, Jeff Johnson wrote:
[...]
Actually not regex.h any more.
How this? regex.h is part of the Single Unix Specification and hence
should be available via your standard libc. It should be
unconditionally
available
On Wed, Apr 15, 2009, Jeff Johnson wrote:
[...]
Thank you! Don't forget the decimal in python2.5. No hury
whatsoever, I don't care much as long as I can build.
But others will care.
This is now also implemented in RPM_CHECK_LIB...
Ralf S. Engelschall
On Apr 15, 2009, at 10:54 AM, Ralf S. Engelschall wrote:
On Wed, Apr 15, 2009, Jeff Johnson wrote:
[...]
Thank you! Don't forget the decimal in python2.5. No hury
whatsoever, I don't care much as long as I can build.
But others will care.
This is now also implemented in RPM_CHECK_LIB...
On Mon, Apr 13, 2009, Ralf S. Engelschall wrote:
On Mon, Apr 13, 2009, Michael Jennings wrote:
-- skipping not existing local sub-directory: xz
configure: error: unable to find internal XZ libLZMA library
Was something omitted from the release tarball?
Yes, the XZ, PCRE and Syck were
On Mon, Apr 13, 2009, Michael Jennings wrote:
[...]
Yes, the XZ, PCRE and Syck were added to RPM 5.1 recently but a
corresponding entry in the top-level Makefile.am's EXTRA_DIST was
forgotten and hence those subdirs were not picked up into the
release tarball. Already fixed in CVS. But I
On Mon, Apr 13, 2009, Jeff Johnson wrote:
[...]
My only interest in internal stuff is to prevent
rpm development from coming full-stop for years
because distros choose not to say, distribute xar,
or change system Berkeley DB. Other than that,
internal is a huge waste of time and energy.
On Apr 13, 2009, at 3:10 PM, Ralf S. Engelschall wrote:
Unfortunately, building with the external libraries is not an option
for me. So I guess I'm stuck with 5.1.7 unless I decide to build
myself a new 5.1.8 tarball from CVS
Ok, 5.2a4 will have this fixed. But for 5.1.9 I really would
