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)


 * Dol-sen (talk) 00:13, 10 February 2015 (UTC) Fixed, thanks

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)


 * Dol-sen (talk) 00:15, 10 February 2015 (UTC) >=sys-apps/portage-2.2.16. Fixed in the Project page.

Updates
I've updated all three areas of concern — The preceding unsigned comment was added by Dol-sen (talk • contribs) 6 February 2015‎
 * 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.


 * Thank you for the clarification. - Poncho (talk) 00:48, 10 February 2015 (UTC)

I think it would be good to highlight the sync-plugin-portage USE flag for layman a bit more. I just spent ten minutes getting annoyed of portage telling me "unsupported value: 'laymansync'", because I missed the one rather inconspicuous sentence mentioning I would need it. Houseofsuns (talk) 17:33, 19 February 2015 (UTC)


 * Done, thank you Dol-sen (talk) 02:40, 21 February 2015 (UTC)

Some Updates
Some suggestions for changes/updates:


 * It still says >=sys-apps/portage-2.2.16 and >=app-portage/layman-2.3.0 would be coming soon, while both have been released now for a while.


 * Done, thanks. Dol-sen (talk) 02:54, 21 February 2015 (UTC)


 * The note As a result of the default auto-sync = True/Yes setting, commands like "eix-sync", "esync -l", "emerge --sync && layman -S" will cause many repositories to be synced multiple times in a row. Please edit your configs or scripts to adjust for the new operation. should probably be updated a bit. AFAICT by dropping '*' from /etc/eix-sync.conf this problem can be avoided and every repository will be synced only once.


 * Please provide a real example /etc/eix-sync.conf file. I looked over the man page, but there are too many options and my system does not have one.  I don't use eix.  Dol-sen (talk) 02:54, 21 February 2015 (UTC)

Small typo in commands
There is no escape characters for symbol  in the commands in section  2.2.2.2 layman-updater Method:

The correct will be:

Gragory (talk) 19:05, 11 March 2015 (UTC)


 * Fixed, thanks Dol-sen (talk) 20:20, 11 March 2015 (UTC)

Another typo
this:

and this:

should be run as root.


 * Fixed, thanks... Dol-sen (talk) 19:01, 5 April 2015 (UTC)

FEATURES="webrsync-gpg"
A short mention in this article pointing to this FEATURE would be nice. --Charles17 (talk) 10:07, 22 May 2015 (UTC)

Location for local overlay
The location line in Example local overlay sync-able from a git backup:  should include the overlay name. Otherwise multiple local overlays would drop their stuff in the same directory.

So why not use  for this example.

And, could you drop some words about what to use as the default location for overlays? --Charles17 (talk) 09:37, 26 May 2015 (UTC)


 * Replying to an old discussion. At this point the default location for all overlays should be, so the example in the article is stale. I'll update these bits. Thanks! --Maffblaster (talk) 19:40, 29 July 2022 (UTC)

Running sync as user and not root
Shouldn't we have this written as "root# " to avoid confusion? Although a user in the portage group should be able to do this, I don't think it should be written that way in the wiki (already had questions about it in the IRC channel). --Rypervenche (talk) 00:25, 21 August 2016 (UTC)


 * Looks like fixed the references before you commented! Thanks for the input. --Maffblaster (talk) 03:56, 22 August 2016 (UTC)

Grammar mistakes
Every time "it's" appears in the article, it should instead be written "its". — The preceding unsigned comment was added by Stqn (talk • contribs) 16 October 2016‎


 * True. Someone please fix this. - dcljr (talk) 03:07, 5 January 2017 (UTC)


 * Fixed. --Maffblaster (talk) 05:28, 5 January 2017 (UTC)

Exposed wikicode
There is exposed wikicode (due to a typo) in the Operation section:
 * "Primary control of all sync operations has been moved from {{c|emerge to emaint."

The template needs to be closed after the word "emerge". - dcljr (talk) 03:05, 5 January 2017 (UTC)


 * Fixed. --Maffblaster (talk) 05:28, 5 January 2017 (UTC)

sync-depth is deprecated
It should be changed to. --Alec (talk) 23:43, 6 July 2018 (UTC)


 * Welp, not deprecated anymore! --Alec (talk) 01:52, 12 July 2018 (UTC)