| 1 |
On Mon, 9 Jul 2018 12:21:36 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> All, |
| 5 |
> |
| 6 |
> is there a tracker for when the portage tree can be moved out of |
| 7 |
> /usr/portage by default? |
| 8 |
> |
| 9 |
> If not, what is the status of us being able to do this? |
| 10 |
> |
| 11 |
> Thanks, |
| 12 |
> |
| 13 |
> William |
| 14 |
> |
| 15 |
|
| 16 |
I don't recall a tracker bug ever being created. |
| 17 |
|
| 18 |
It required the stages be generated by catalyst-3 which can be |
| 19 |
configured to any location for the tree defaults. catalyst-2 had paths |
| 20 |
hard-coded all over the place, plus used those paths as keys in |
| 21 |
python dictionaries... |
| 22 |
|
| 23 |
I believe all stages are now built with catalyst-3 for all arches, but |
| 24 |
I don't know about some of the lesser used arches as some of those are |
| 25 |
older dates. |
| 26 |
|
| 27 |
That and a portage release with the new default location set in it's |
| 28 |
backup configs. |
| 29 |
|
| 30 |
So, it should be ready to convert if the minor arches stage are being |
| 31 |
generated with catalyst-3 |
| 32 |
|
| 33 |
-- |
| 34 |
Brian Dolbec <dolsen> |
Archives