Now, temporary folders are assigned to packages in the following manner: Usefully there’s a symbolic link from the package folder to this temporary folder, so now this can be accessed in install/run scripts as: $. This is a requirement for DSM 7.0: os_min_ver="7.0-40000"īefore, I was using the system wide temporary folder for storing some temporary files: ( volume1 changes to whatever the volume is called, which might be different on multiple drive machines). The first thing is that unless you have a Synology device capable of running Virtual Machine Manager you’re going to have to get a new device or stop supporting DSM 6.x, because you can’t downgrade from DSM 7.0 back to DSM 6.x again. But just in case this does help other package developers, here’s a list of the stuff I had to change… I’ve left this to last because fewer people will be interested in this. Unfortunately this means existing licences will have to be re-installed. As the user is changing from root to bliss this means licence information will be lost. LicencesĬurrently, licence information is stored in a space of storage for the user. If Synology don’t provide an official package, we’ll have to do something similar. I’m hoping Synology provide a one-click “do you give permission for this app to change your music files”-style challenge… JavaĪt this time, there’s no official Java package in the DSM 7.0 Package Center.ĭuring my testing I used rednoah’s excellent java-installer to select the correct JVM. Click Edit > Permissions and then change the Local users dropdown to System internal user. This must be added via Control Panel > Shared Folder > music. What this means is that, by default, bliss doesn’t have read or write access to the Music share. Before, packages often ran as root which is a superuser capable of doing anything on the NAS. Perhaps the biggest change in DSM 7.0 for package developers are new constraints on permissions. Either approach would avoid having to choose a version. This is a bit of a pain, so I’d like to introduce a Package source soon, or be featured on the official Synology Package Center. This means there will now be two versions of the. SPK file has to be different between the pre-DSM 7.0 and DSM 7.0 versions. It’s a new requirement that the metadata embedded in an. SPKs in two ways: by downloading them and manually installing them, or via a Package source (some call it a repository). SPK is the file that encompasses a Synology package. There are changes in DSM 7.0 which means a little more work from the installer. Given a few pre-requisites (see below) bliss installs and runs as before.I'll leave the instructions/thoughts below for anyone else integrating with DSM 7.0 who might find them useful. DSM 7.0 is now shipping and we've introduced our own Synology package repository to download the DSM 7.0 version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |