Date: Sat, 7 Jun 2014 21:10:15 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Vick Khera <vivek@khera.org> Cc: FreeBSD Ports List <ports@freebsd.org> Subject: Re: splitting subversion port? Message-ID: <475041294.20140607211015@serebryakov.spb.ru> In-Reply-To: <CALd%2BdccJVqa2MnzQw5PyEA47M3Uvn9QGpaCF8f1cT3FXgwm7_Q@mail.gmail.com> References: <CALd%2BdccJVqa2MnzQw5PyEA47M3Uvn9QGpaCF8f1cT3FXgwm7_Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Vick. You wrote 22 =D0=BC=D0=B0=D1=8F 2014 =D0=B3., 22:18:10: VK> I was wondering if you would be open to peeling off the mod_dav_svn VK> from being an option in the subversion port to being its own port that VK> depends on this one, or making a sub-port that installs subversion VK> with it enabled under a different package name. VK> The reason I have is that I am trying to switch over to pkgng and VK> using pre-built packages for everything. I can't do this for VK> subversion as I need the dav module on one server, but not on any VK> other machine I run. Also, I use another apache module, VK> www/mod_authnz_crowd, which depends on a subversion built with VK> mod_dav_svn. As it stands, I cannot make a package for that easily. VK> There is precedent for splitting the apache module out, as PHP5 has VK> recently done just that. VK> By splitting the module out into its own port, all of this would be VK> possible, and it would avoid having to install the module-enabled VK> package on all of my servers which would pull down apache, as well, VK> which I do not need on my compute nodes. VK> Another way of accomplishing the goal would be to make a sub-port VK> similar to things like emacs-nox11 and ImageMagick-nox11 that install VK> their base ports with specific options. There could be a VK> subversion-apache port that builds the subversion port with the apache VK> module and dependencies. VK> Anyhow, I'm willing to try to do the work, but I wanted to know if VK> you're agreeable, and which way you'd prefer to do it. Obviously the VK> sub-port would be easier. I have a feeling the split port may not work VK> out because the SVNUSER gets changed if the dav module is enabled. Really, I want to split subversion port to many parts (libraries, client, server, apache port, tools) for many years, but it hard to achieve as subversion build system is rather complex one. I'm waiting for "multiple packages from one port" feature in pkg/ng :) --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?475041294.20140607211015>