Project Talk:Portage/Sync

Confusing bit
The article currently says: This is unnecessarily confusing. I assume this means auto-sync can be set to any one of the 4 possible settings, and that yes and true are synonymous, as are no and false. All the slashes make this hard to parse.
 * New auto-sync setting for all repository types (needed):

Something like this might be better:
 * New auto-sync setting for all repository types (needed): or  Note that   may used in place of   and   in place of.

Also, it would really be better to add a little context at the beginning of this page to establish what it's talking about before diving into "Changes". - dcljr (talk) 22:23, 6 February 2015 (UTC)

Plug-in sync portage version
In the "Alternate method" section, it says:
 * Migrating from the old make.conf layman conf_type to repos.conf type:
 * 1) Ensure you have the new plug-in sync portage version installed

And what version is that, exactly? - dcljr (talk) 22:35, 6 February 2015 (UTC)

Updates
I've updated all three areas of concern


 * Thanks! - dcljr (talk) 03:33, 7 February 2015 (UTC)

laymansync
What's the advantage of using  over   for an overlay hosted on git? Poncho (talk) 16:15, 9 February 2015 (UTC)


 * Dol-sen (talk) 00:12, 10 February 2015 (UTC) For most git overlays, almost none.  Currently layman will automatically set the sync-type to layman-sync when you add an overlay.  So from a user perspective, it does not require any manual editing.  The real advantage is that layman currently has more features capability with git than is currently available in portage.  Like git branch support, and configurable git_syncopts.  But that will change.  I just wanted to get the new system being used before we wait and wait for more and more features to be added before releasing the new system.