| 1 |
On Mon, 2 Feb 2015 16:54:37 -0800 Brian Dolbec wrote: |
| 2 |
> Attached is an updated news item. |
| 3 |
[...] |
| 4 |
|
| 5 |
> Changes: /etc/portage/repos.conf/* |
| 6 |
> New for all repository types (needed): |
| 7 |
> auto-sync = yes/no, true/false # default if absent: no/false |
| 8 |
|
| 9 |
1. Why autosync is disabled by default? This broke current |
| 10 |
default for emerge --sync. And if users added overlays, they |
| 11 |
most definitely want them to by synced by default as well. |
| 12 |
So I propose to set auto-sync=yes by default. |
| 13 |
|
| 14 |
2. Why not to keep compatibility with current layman and |
| 15 |
local repositories? On some systems I have about dozen of |
| 16 |
overlays and I bet most users too. Give people time to adapt |
| 17 |
their setups for new changes, e.g. keep support for old |
| 18 |
configs and behaviour for at least several minor version bumps. |
| 19 |
|
| 20 |
3. I suppose eix-sync will be completely broken with |
| 21 |
portage-2.2.16? That's nuts. Really. Give developers time to |
| 22 |
adapt their software for new API. Be compatible, at least for |
| 23 |
a while. |
| 24 |
|
| 25 |
Best regards, |
| 26 |
Andrew Savchenko |
Archives