1 |
Currently there are still some old ebuilds for coda in portage. |
2 |
They are named coda-client and coda-server. The more recent |
3 |
ebuilds are all called coda, so I would like to get rid of |
4 |
the older ones to prevent confusion. |
5 |
|
6 |
I have read about using /usr/portage/profiles/updates/* for |
7 |
making sure that people who are using older ebuilds automatically |
8 |
get the new ones when they are moved between categories, but |
9 |
I am not sure that this is the right mechanism to use in |
10 |
coda's case. It's also not clear to me if this wouldn't |
11 |
cause problems as two packages are sort of moved into one. |
12 |
|
13 |
Can anyone explain the proper procedure or refer me to some |
14 |
documentation? |
15 |
|
16 |
Thank, |
17 |
Maurice. |