First of all: Thanks for the ebuilds! Anyway, the pkg_postinst() is quite confusing. It says you should create a _directory_ for snapshots. Instead it seems essential that if you use BTRFS $SUBVOLUME/.snapshot is a BTRFS-snapshot itself. I don't know the behaviour at ext4 but I suggest to use snapper for creating configs itself: pkg_postinst() { elog "In order to use Snapper, you need to set up" elog "at least one config first. To do this, run:" elog "snapper create-config <subvolume>" elog "For more information, see man (8) snapper or" elog "http://snapper.io/documentation.html" } Reproducible: Always
True, although .snaphots should be a subvolume, not a snapshot ;) But yes, I wasn't aware of create-config setting it all up automatically when I wrote the ebuild, so your suggestion makes sense. Lan, can you update the ebuild with this? I'm not really sure what the ebuild update process is supposed to be, since I wasn't the one who submitted the file to the main repository...
(In reply to Dainius Masiliūnas from comment #1) > True, although .snaphots should be a subvolume, not a snapshot ;) Oops, my fault. Of course a subvolume, containing the snapshots ;D > But yes, I wasn't aware of create-config setting it all up automatically > when I wrote the ebuild, so your suggestion makes sense. > > Lan, can you update the ebuild with this? I'm not really sure what the > ebuild update process is supposed to be, since I wasn't the one who > submitted the file to the main repository... Thx.
+ 30 May 2014; Yixun Lan <dlan@gentoo.org> snapper-0.2.2-r1.ebuild, + snapper-9999.ebuild: + fix bug #511410, thanks Dainius Masiliūnas,holgersson; combine minor + improvement suggested by @jlec + fixed without revision bump, thanks all
