Alan Fry wrote on Mon, 24 Aug 2020 15:46 -0400:
> This time, to the whole group.
>
> On Wed, Aug 19, 2020 at 1:45 PM Alan Fry <ttlx0100_at_gmail.com> wrote:
>
> >
> >
> > On Mon, Aug 17, 2020 at 11:19 PM Nathan Hartman <hartman.nathan_at_gmail.com>
> > wrote:
> >
> >>
> >> Hi Terry,
> >>
> >> Based on some quick searches, it looks like the Synology NAS is an
> >> ARM-based machine and runs a Linux distro which is Debian-based and
> >> customized by Synology. Assuming I'm correct (let me know if not),
> >> that tells me that the build should be done on an ARM-based machine
> >> (which might be the NAS itself).
> >>
> >
> > Hello Nathan (yes email says Alan, I use this account for lists).
> >
> > I did some research on this. I assumed the same as you did, I'd build on
> > the NAS itself, but Synology has a toolkit which describes how to make the
> > various targets (ARM and some others they use, including intel) for the
> > Synology package. This is done with cross compiling from what I have read.
> >
> >
> >>
> >> Does Synology provide any documentation or examples to help software
> >> packagers? One thing you'll need to know in particular is whether a
> >> package for Synology is really just a Debian ".deb" package for APT,
> >> perhaps with some special sauce added to provide a one-click install
> >> icon or something. If it is, then a package for another Debian-based
> >> distro might be a starting point.
> >>
> >
> > Good question, I'll see if I can get some answers on this. Again, not
> > from the Linux world :).
I disagree with the recommendation to check whether Synology's packages
are .deb packages. .deb files are just ar(1) archives, but in order to
build a package there is a lot more to know than just what file format
to use. For example, .deb files embed executable code that runs at
installation time, and a distro may have its .deb packages do
distro-specific things in those hooks. Therefore, I recommend that you
focus on finding the documentation for packagers, as Nathan wrote at
the start.
.deb files are in general not portable to distro versions other than
the one they were built for: something built for Debian 9 can't be
assumed to be installable even on Debian 10. They _might_ work in
other cases, but then again, they might not.
> >>
> >> If you're not comfortable with Linux yet, you might want to experiment
> >> with it on a virtual machine first, to reduce the risk of messing up
> >> your NAS with a wrong administrative command. With a virtual machine,
> >> you could also practice building SVN on Linux.
> >>
> >
> > Yes, I built a VM with Ubuntu installed into it. I've used linux off/on
> > over the years, but nothing more than very simple work. I actually tried
> > to build SVN, pulled the tarball down and followed the directions ... but I
> > came to a point where I decided to stop and regroup.
You might want to post more details (what exactly you did, what the
output was, and what you don't understand about it).
> >> 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. If later on you wish to hack on SVN on Windows, having a working
> >> build environment will be helpful for that too. :-)
> >>
> >
> > I've always found that the setup/config so you can actually develop
> > something is the harder part :).
That's called writing a hello world program.
Received on 2020-08-26 12:21:51 CEST