On Mon, Aug 15, 2005, Ralf S. Engelschall wrote: > This I don't understand, Christoph. Subversion 1.2.1 already contains > a local copy of exactly Neon 0.24.7 in its subdir neon/. What you are > doing here seems like adding another unnecessary copy into neon/neon/.
Yes, you are right, if overseen the exisiting neon directory. The primary reason I've done this cause I wanted to avoid any external neon libs since they have to match certain versions which are not always fulfilled (e.g. Subversion python bindings are broken in 2.4 release since neon package in 2.4 is too new). Nevertheless I don't wanted to rely on neon brought by subversion since this isn't "safe" against local modifications hence I preferred a vanilla version from http://www.webdav.org/neon/. You are right, currently there is now diff between the vanilla version of neon and the one included in subversion but this might change in the future. Maintaining a vanilla version might be easier in means of security patches etc. BTW for similar reasons I'm not too happy abount pining Swig to a certain version. While this solution works now it doesn't scale. What if there's another package requiring a different version of Swig? IMHO it's better to add outdated software versions to the packages which require them (keep the swig package up to date; include old swig version into subversion package). > I've backed out this part of your patch now as the local copy contained > in the Subversion 1.2.1 tarball is already sufficient. Could we MFC my remaining changes to fix 2.4 relase? > Additionally, > I've now removed the NEON installation files, as I don't see why > Subversion needs them under its run-time. I wasn't sure about this one so I decided to keep them. Honestly, I don't have any experience with this python stuff and haven't had time last week to test it with some software that uses it. In the meantime I packaged Trac (http://www.edgewall.com/trac/), maybe I have some time next few days to play around with it. I'll commit the packaged if it works. -cs ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
