[bug-notifications] [libproxy 0004307]: split libproxy package to remove X deps

[Mantis Bug Tracker]

The following issue has been set as RELATED TO issue 0004281. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=4307 
====================================================================== 
Reported By:                bwalton
Assigned To:                hson
====================================================================== 
Project:                    libproxy
Issue ID:                   4307
Category:                   packaging
Reproducibility:            N/A
Severity:                   tweak
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-02-25 16:47 CET
Last Modified:              2010-02-26 21:25 CET
====================================================================== 
Summary:                    split libproxy package to remove X deps
Description: 
Hi Roger,

What are your thoughts about splitting libproxy into libproxy-core,
libproxy-gnome, etc.  I'd like to get the core bits without dragging in
half of X.  For example, I shouldn't need all of the X libs to install svn
which has indirect dependencies on libproxy.

Thanks
-Ben
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0004281 Causes subversion to pull in X11 libs (...
====================================================================== 

---------------------------------------------------------------------- 
 (0007533) dam (administrator) - 2010-02-26 21:25
 http://www.opencsw.org/mantis/view.php?id=4307#c7533 
---------------------------------------------------------------------- 
There is no direct dependency from svn to libproxy, it is svn -> neon ->
libproxy. I have now added alternatives for neon, one with minimal
dependencies without libproxy and one with full dependencies including
libproxy, so the immediate need may be leveled.

Additionally, the same mechanism can be applied here for alternatives on
libproxy, one minimal without X11 and one with full dependencies. The
mechanism is not straight-forward, I'd be happy to give you a hand. Maybe
on the next 0.4 update?