On Tue, 3 Feb 2015 17:37:49 +0300 Andrew Savchenko wrote: > On Mon, 2 Feb 2015 16:54:37 -0800 Brian Dolbec wrote: > > Attached is an updated news item. > [...] > > > Changes: /etc/portage/repos.conf/* > > New for all repository types (needed): > > auto-sync = yes/no, true/false # default if absent: no/false > > 1. Why autosync is disabled by default? This broke current > default for emerge --sync. And if users added overlays, they > most definitely want them to by synced by default as well. > So I propose to set auto-sync=yes by default. > > 2. Why not to keep compatibility with current layman and > local repositories? On some systems I have about dozen of > overlays and I bet most users too. Give people time to adapt
s/most/many/ > their setups for new changes, e.g. keep support for old > configs and behaviour for at least several minor version bumps. > > 3. I suppose eix-sync will be completely broken with > portage-2.2.16? That's nuts. Really. Give developers time to > adapt their software for new API. Be compatible, at least for > a while. 4. I don't fully understand how new plugin system is supposed to interact with layman. I far as I can see, the global goal is to replace layman by new sync system: it already supports git and svn, which covers most of overlays. For more exotic ones there is a laymanator sync-type. If I'm right in my guess above, a question arises: how users should maintain overlays via sync plugins then? Right now layman is very convenient in adding and removing overlays: user needs only to provide overlay name and have a nice list of overlays available. With sync-plugins approach one have to enter all sync-uri paths manually, which is annoying at least, irritating at last, since many parameters have to be entered manually: location, sync-type, sync-uri, auto-sync. Is there any tool to manage this stuff in a friendly way? Best regards, Andrew Savchenko
pgpHsUAzum1Lz.pgp
Description: PGP signature
