Date: Sat, 07 Jun 2014 23:25:40 +0200 From: olli hauer <ohauer@gmx.de> To: FreeBSD Ports List <ports@freebsd.org> Cc: Vick Khera <vivek@khera.org>, lev@FreeBSD.org Subject: Re: splitting subversion port? Message-ID: <53938354.3090806@gmx.de> In-Reply-To: <475041294.20140607211015@serebryakov.spb.ru> References: <CALd%2BdccJVqa2MnzQw5PyEA47M3Uvn9QGpaCF8f1cT3FXgwm7_Q@mail.gmail.com> <475041294.20140607211015@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-06-07 19:10, Lev Serebryakov wrote: > Hello, Vick. > You wrote 22 мая 2014 г., 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 :) > > This should be possible if the old pkg tools are no longer supported (this year Sept.) and code for sub packages is in the tree. Splitting the package now into several ports is not a preferred way. Building a full blown subversion triggers without sub packages x times a full build for every single shaped port (see for example bacula server/client) -- olli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53938354.3090806>