You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Julian Foad <ju...@apache.org> on 2019/06/19 08:29:03 UTC

Docker Svn build environment [was: Subversion's community health]

Paul Hammant wrote:
> Michael Pilato wrote:
>> Paul Hammant wrote:
>>> Nobody is going to roll up to contribute to 1.x or 2.x Subversion if 
>>> there is no copy-pasteable instructions for building on Mac, Win and Linux. 

>> Is there an opportunity here for someone to whip up a Dockerized 
>> development environment for Subversion?  Volume mapped to local disk for 
>> easy editing of source code in your tool of choice, but all the 
>> dependencies and such present in the image?  Just thinking out loud here...
> 
> Dockerized build templates would be great for a quickstart. I might have 
> one or two for Svn and if I de-hack them might be shareable. They'd be 
> biased towards Linux for build/test/standup of course, but would be 
> better than nothing.

That would be awesome. It could remove the biggest barrier to entry for 
many developers.

Docker is a good choice for this, and I am convinced we'll get the best 
outcome if we pool our resources into supporting one way well, so count 
me in.

- Julian

Re: Docker Svn build environment [was: Subversion's community health]

Posted by Paul Hammant <pa...@hammant.org>.
People wanting to donate a feature or fix a bug with Subversion are
increasingly going to be happy with a Docker-based quick start. Most
F/OSS teams want tests too, and y'all are very strict there in that
regard, and someone who can write tests for your test-base covering
code for your codebase is most likely going to be super-OK with
Docker.  Where that incentivized groups is left with pause for thought
is on the consumption of contributions and the schedule for seeing
consequential releases.

Now, there's another group who want to image machines and shove in
"latest released" Subversion. Their problem is downstream maintainers
of operating systems for one, and the lack of comprehensive
Svn-dev-team install instructions to overcome maintainer choices
secondarily.  Ubuntu's at 19.04 now, and it's shipping Svn 1.10.  The
Mac's homebrew is at 1.12 presently, but it is quite often months
behind. This group is happy to build from source (if that is reliable)
and would use any on-platform or cross-compilation script to target
the machine/OS they're interested in. They may not care to edit
source. They may even be happy to skip tests - they just want the
binaries in situ.

How much of the first group would not want to wait for releases, and
instead deploy unreleased versions of Subversion?  Meaning they've
donated a patch, have some assurances that it is being accepted as it
meets standards, but don't want to wait any longer before
productionizing it to some level?

Re: Docker Svn build environment [was: Subversion's community health]

Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Jun 19, 2019 at 6:36 AM Julian Foad <ju...@apache.org> wrote:

> Some time within the past year I looked for the best available Docker
> deployment of Subversion and found this:
>
> https://github.com/elleFlorio/svn-docker
> "Lightweight Docker image to build a container running an SVN server"
>
> It might be helpful as a starting point for creating a dev environment.
>
>
This seems like it could be useful for some dev situations and making it
easier to run tests but I otherwise do not see the value in it.  People on
Windows and OSX ultimately want binaries that will run on their OS.  On
Linux you want something that will work natively on your distro.  This will
do nothing to assist with that.

It would make it easier to throw together a patch and run the tests but
ultimately I would expect someone doing this would probably also want to
run with their version of the binary they built.

By all means, we could create this but we should not make the mistake of
believing it solves the main problems.


Mark Phippard
http://markphip.blogspot.com/

Re: Docker Svn build environment [was: Subversion's community health]

Posted by Julian Foad <ju...@apache.org>.
Some time within the past year I looked for the best available Docker 
deployment of Subversion and found this:

https://github.com/elleFlorio/svn-docker
"Lightweight Docker image to build a container running an SVN server"

It might be helpful as a starting point for creating a dev environment.

- Julian