[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN on Synology

From: Alan Fry <ttlx0100_at_gmail.com>
Date: Mon, 24 Aug 2020 15:46:43 -0400

>
>
> Alan Fry wrote on Wed, 19 Aug 2020 13:52 -0400:
> > On Tue, Aug 18, 2020 at 7:28 AM Daniel Shahaf <d.s_at_daniel.shahaf.name>
> > wrote:
> >
> > > Nathan Hartman wrote on Mon, 17 Aug 2020 23:19 -0400:
> > > > Since you're a Windows developer, getting SVN building on Windows
> > > > might be a good first step to get acquainted in an environment you
> > > > know.
> > >
> > > I'm not so sure about this, actually. The Windows and non-Windows
> build
> > > processes have little in common beyond the names of dependency packages
> > > that should be installed. Furthermore, the non-Windows build should
> > > usually take advantage of $distro's facilities, which only makes it
> more
> > > different to the Windows build. (E.g., there's no Windows equivalent
> of
> > > «apt-get build-dep subversion».)
> > >
> >
> > Synology has a package toolkit, which I'm diving into. It's interesting,
> > it seems they cross-compile to create their packages.
> >
> >
> > >
> > > Operationally, I second Nathan's idea of first getting a Linux VM and
> > > building on that for practice. The distro should ideally be Synology,
> > > or failing that, whatever Synology is based on (check /etc/os-release
> > > and /etc/apt/sources.list* (sic) on the NAS).
> > >
> >
> > Got that, I built a Ubuntu machine in VirtualBox and I can get around
> > fairly easily. I did try to build SVN, but... didn't get far.
> >
> >
> > >
> > > We _would_ welcome help with the Windows build, of course; it's just
> > > that knowing how to build on Windows isn't going to acquaint you with
> > > building on Linux. For that, you'll learn more from building some
> > > random package with few dependencies — say, rsync — on Linux.
> > >
> >
> > I think the big challenge for myself is just learning enough to build the
> > targets. Synology has various processors, ARM etc, and I'd have to build
> > (effectively) SVN for all of Synology's hardware. I'm assuming the
> install
> > package when run figures out which one to actually install. Synology
> has a
> > SDK for all this, which again, I'm looking into.
> >
> >
> > >
> > > Separately: What problem are you trying to solve? Why are you
> > > looking into building your own packages?
> > >
> >
> > Honestly... I have SVN on my NAS... and I upgraded, and happen to notice
> > that the SVN pkg was rather old. I reached out to Synology and they
> > confirmed that the third party that created those packages wasn't
> producing
> > anymore.
> >
> > I probably could take the intel version (since my new Synology NAS is
> intel
> > based) and hack it, but that fixes just my NAS. I could do other
> methods,
> > but I like the idea that the NAS has SVN running 24x7.
> >
> >
> > >
> > > Cheers,
> > >
> > > Daniel
> > >
>
>
Received on 2020-08-24 21:46:59 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.