-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 15/05/15 12:15 PM, Diamond wrote: > On Fri, 15 May 2015 08:23:27 -0700 Dirkjan Ochtman <d...@gentoo.org> > wrote: > >> On Fri, May 15, 2015 at 7:51 AM, Michał Górny >> <mgo...@gentoo.org> wrote: >>> Starting with Portage 2.2.19, a new SquashDelta syncing method >>> has been introduced. It is meant to provide lightweight and >>> efficient solution for stable systems. The whole repository is >>> contained within a single pre-generated SquashFS image file. >>> The daily snapshot of the repository is first fetched from the >>> mirrors, and afterwards updated in-place using deltas (without >>> repacking). >> >> This sounds nice, but the news item currently leaves me wondering >> what sort of improvements I should expect. [...] > > I've read the pdf article of Michał Górny and from my expirience > with emerge-delta-webrsync and app-portage/getdelta in the past > this good old new feature looks mostly useful for bad Internet > connections (too slow or too expensive ones) and looks mostly > useless for syncing relative to rsync method from local mirror like > I use [...]
Although this thread should be a review of the news item rather than a review of the feature, I think both of these guys have a point. The main benefit to this new feature is that it allows users to use a squashfs image for their gentoo repo (portage tree) without having to (re)generate it themselves locally every time they --sync, AND without having to re-download an entire image from gentoo mirrors each time either. The new item doesn't really cover this much -- that the feature is for supporting storage and synchronization of the gentoo repo on squashfs rather than on a regular filesystem. Perhaps it would be enough to link to an article describing the benefits of using a squashfs'ed portage tree, so users could chose whether they want this or not based on that? Similarly, it would probably be good to mention that this new feature deprecates squash_portage and the other tools/methods out there for doing the same thing locally. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlVWO9kACgkQ2ugaI38ACPA1vwD9ELIdOgSSTfly3rT5zU6dzhGb 62LtN8loiRFhKfyAe/8A/24xw95j7qav/himVRA5OOjM3qTE++iBY/2yXPgLWpI5 =1+2r -----END PGP SIGNATURE-----
