| 1 |
Bo Ørsted Andresen wrote: |
| 2 |
> On Monday 26 June 2006 14:36, Sean wrote: |
| 3 |
>> What is the best way to handle the files that etc-update states needs to |
| 4 |
>> be updated? |
| 5 |
> |
| 6 |
> There are three competing utilities for this purpose. The official etc-update |
| 7 |
> (which sucks and should have been deprecated a long time ago... ;) ), |
| 8 |
|
| 9 |
What's bad about etc-update or what's missing? |
| 10 |
|
| 11 |
> dispatch-conf and cfg-update. |
| 12 |
|
| 13 |
Hm, where are the advantages of dispatch-conf over etc-update? I |
| 14 |
just used dispatch-conf for the first time, and it seems to be |
| 15 |
very much like etc-update, but it doesn't even display the list |
| 16 |
of files that need to be updated nor does it seem to offer a way |
| 17 |
to accept all changes (which are left). |
| 18 |
|
| 19 |
>> Or could anyone suggest the best steps to proceed? |
| 20 |
> |
| 21 |
> What you should do is figure out how to use either dispatch-conf or |
| 22 |
> cfg-update. |
| 23 |
|
| 24 |
Hm. Why? What's bad about etc-update? |
| 25 |
|
| 26 |
Alexander Skwar |
| 27 |
-- |
| 28 |
Some people pray for more than they are willing to work for. |
| 29 |
-- |
| 30 |
gentoo-user@g.o mailing list |
Archives