Michael Weiss 351f5fc585 fuse3: init at 3.1.1 ... This includes fuse-common (fusePackages.fuse_3.common) as recommended by upstream. But while fuse(2) and fuse3 would normally depend on fuse-common we can't do that in nixpkgs while fuse-common is just another output from the fuse3 multiple-output derivation (i.e. this would result in a circular dependency). To avoid building fuse3 twice I decided it would be best to copy the shared files (i.e. the ones provided by fuse(2) and fuse3) from fuse-common to fuse (version 2) and avoid collision warnings by defining priorities. Now it should be possible to install an arbitrary combination of "fuse", "fuse3", and "fuse-common" without getting any collision warnings. The end result should be the same and all changes should be backwards compatible (assuming that mount.fuse from fuse3 is backwards compatible as stated by upstream [0] - if not this might break some /etc/fstab definitions but that should be very unlikely). My tests with sshfs (version 2 and 3) didn't show any problems. See #28409 for some additional information. [0]: https://github.com/libfuse/libfuse/releases/tag/fuse-3.0.0		2017-09-21 23:59:46 +02:00
..
darwin	Revert "Merge commit on master into staging"	2017-09-15 13:01:12 -04:00
gnu	all-packages: Remove forcedNativePackages; we no longer need it	2017-09-20 00:59:19 -04:00
linux	fuse3: init at 3.1.1	2017-09-21 23:59:46 +02:00
windows	wxMSW: Fix syntax --- travis eval did not catch	2017-06-28 22:31:24 -04:00