Packaging issues - dependent packages

Right now I'm packaging up the apr-2001-09-28.tar.gz and
neon-0.17.1.tar.gz source files along with the pristine
subversion-M3-r(release).tar.gz files in the RPM src package. Is this the
way it is intended long term or will/should the neon and apr packages be
able to used as separate packages that subversion depends on?

Either way is fine, I just didn't know what the developers wanted long
term. If the neon and apr are general-purpose useful for other things
then we might want to transition to them being separate packages installed
outside the subversion package with appropriate dependencies.

I am also working with a friend to develop Solaris PKG packages and hope
to add those to the packages subdirectory in the near future.

I also had a request to be able to install the binaries in non-standard
places so that users without root access could install it. I'm working on
that now.

Latest Subversion RPM packages: Revision 265
==============================================
ftp://summersoft.fay.ar.us/pub/linux/RPMS/i386
ftp://summersoft.fay.ar.us/pub/linux/RPMS/src

-- 
David Wayne Summers          "Linux: Because reboots are for upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org