| 1 |
Daniel Pielmeier schrieb: |
| 2 |
>> OK, I'll try again tomorrow. |
| 3 |
>> This does prompt a couple questions: |
| 4 |
>> |
| 5 |
>> 1. How does one know when not to do a sync/update so that one |
| 6 |
>> can avoid these problems? Is there a database broken |
| 7 |
>> ornot-broken status? |
| 8 |
>> |
| 9 |
>> 2. Is there no way to "commit" a set of database changes so |
| 10 |
>> that the database doesn't have to be left in a broken state |
| 11 |
>> during moves? (Maybe I'm just spoiled using Subversion...) |
| 12 |
> |
| 13 |
> 1. You can not know before but you can monitor the irc channel |
| 14 |
> #gentoo-commits on freenode or the gentoo-commits mailing list. So you |
| 15 |
> know which changes are done to the portage tree. Be careful this will |
| 16 |
> cause heavy traffic to your inbox. |
| 17 |
> |
| 18 |
> 2. I don't know if this is doable in one go. The gentoo package |
| 19 |
> maintainer adds the ebuild to its new place and removes it from its old. |
| 20 |
> When this is done he changes the other ebuilds pointing to the old |
| 21 |
> locations. He also makes an entry in $PORTDIR/profiles/updates so the |
| 22 |
> /var/db/pkg is updated accordingly for already installed packages. |
| 23 |
> |
| 24 |
> Regards, |
| 25 |
> |
| 26 |
> Daniel |
| 27 |
> |
| 28 |
|
| 29 |
As alternative you can also monitor: http://cia.vc/stats/project/gentoo |
| 30 |
-- |
| 31 |
gentoo-user@l.g.o mailing list |
Archives