sklassen commented on issue #38: local.ini sourced from tree on installation URL: https://github.com/apache/couchdb-pkg/pull/38#issuecomment-443668668 @wohali On the last PR, I have built a new snap using the master copy and have push the files to the ubuntu store with both 2.2 (stable) and 2.3 (candidate) `snap install couchdb-sklassen` installs the 2.2 version; `snap refresh --candidate couchdb-sklassen` rolls forward to 2.3 and then, if needed, `snap revert couchdb-sklassen` rolls back. So the new package, builds, installs and rolls forward and back. I'd like feed back if this is working for others. As for your second part, I've also built a new snapcraft.yaml file that uses the debian package. https://github.com/sklassen/couchdb-pkg branch snap_deb_src The BUILD.md has the steps I took. You basically install couchdb on the base system and then copy the couchdb directory to the /snap install directory. It seems to work for me, although I haven't tested it extensively. I only got it to run on 16:04 (couchjs moz lib package issue) with 2.2. It is not at a stage I'd raise a PR for it. Because it copies files from the base system, which is not how the snapcraft is meant to be, and might be disallowed in the future, it's not pretty. Currently, there is no way to add sources during the build stage, although future snapcraft versions might fix this. For the moment, I'm left just coping it from the base system. It would be easier if I could just install apt-get couchdb from within the snap, but that you require couchdb .deb package being in the official package. You can see from the yaml file how I copy across the /opt/couchdb and how the snap_run file and hooks link back to the /snap and the /var/snap directories. For my part, I still prefer building from git or tar. It gives more flexibility and doesn't create a dependency on the deb file. And, further, it is compliant with the current snapcraft guidelines. Still, if you like this method better, you could try it against your base system for 2.3. Cheers Simon On Fri, Nov 30, 2018 at 3:28 PM Joan Touzet <[email protected]> wrote: > @sklassen <https://github.com/sklassen> FYI see apache/couchdb-docker#117 > <https://github.com/apache/couchdb-docker/issues/117> - we discussed this > previously - may be a better way forward for the snap. > > I'll merge this now, but you should consider updating this. > > We are about to release CouchDB 2.3.0 - once the other builds are done > (packages, Docker, Windows, Mac) I will turn my attention back to this > issue. If you've got a PR up by then (probably in 10 days or so) to just > install from our .deb file, that'd be fantastic - will save a ton of work, > keep the snapfile definition fairly static across releases, and would make > me much more comfortable moving future snap releases into the stable > category on the snap store. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/couchdb-pkg/pull/38#issuecomment-443116202>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGrF5Wl9fcGW9wQ2VhxRwx6bYvxu61-Hks5u0N4pgaJpZM4YTD68> > . >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
