| 1 |
On Thu, Feb 28, 2019 at 10:41 AM Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 2 |
> |
| 3 |
> On Thursday, 28 February 2019 08:43:13 GMT Davyd McColl wrote: |
| 4 |
> |
| 5 |
> > Well, that's pretty-much how git works -- that local repo was still pointing |
| 6 |
> > to the old remote. Updating your repos.conf won't change that as the old |
| 7 |
> > remote is stored in config in the .git folder. |
| 8 |
> |
| 9 |
> OK. It'd be helpful if the handbook said that, or somewhere else in the docs. |
| 10 |
> Without that, the clear impression is that repos.conf is the place to specify |
| 11 |
> the remote source. |
| 12 |
|
| 13 |
If you're going to migrate it in-place you really should set it in |
| 14 |
both places. Otherwise you'll end up with a surprise if you remove |
| 15 |
/usr/portage. |
| 16 |
|
| 17 |
In general it is usually simplest to just remove /usr/portage anytime |
| 18 |
you change the sync settings. At least until portage gets smarter |
| 19 |
about it. |
| 20 |
|
| 21 |
-- |
| 22 |
Rich |
Archives