Bug 135049 - Include subversion-javahl subpackage
Summary: Include subversion-javahl subpackage
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: subversion
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Joe Orton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-08 09:50 UTC by Didier
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-06 18:21:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Didier 2004-10-08 09:50:14 UTC
Description of problem:

For Subclipse (http://subclipse.tigris.org), the Eclipse Subversion
plugin, the libsvnjavahl.so library is the preferred way to
communicate with an SVN repository.

This library is part of the Subversion JavaHL component.
The current subversion .spec file does not allow for building the
JavaHL component (see bug #134786).


RHEL is shipped with Eclipse, Java JDK and Subversion, resolving all
dependencies ; modification of the .spec file and the patch as
discussed in bug #134786 would allow for effortless SVN integration in
Eclipse.

Comment 1 Suzanne Hillman 2004-10-14 20:21:50 UTC
Internal RFE bug #135751 entered; will be considered for future releases.

Comment 2 Joe Orton 2007-06-06 18:21:07 UTC
This problem is resolved in the next release of Red Hat Enterprise Linux. Red
Hat does not currently plan to provide a resolution for this in a Red Hat
Enterprise Linux update for currently deployed systems.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects.


Note You need to log in before you can comment on or make changes to this bug.