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».) 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). 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. Separately: What problem are you trying to solve? Why are you looking into building your own packages? Cheers, Daniel
