| 1 |
Am Sonntag, 17. August 2008 10:08:46 schrieb Andrew Gaydenko: |
| 2 |
> ======= On Sunday 17 August 2008, Heiko Wundram wrote: ======= |
| 3 |
> |
| 4 |
> > Am Sonntag, 17. August 2008 09:52:57 schrieb Andrew Gaydenko: |
| 5 |
> > > After last syncing 'emerge -pvDuN world' ends with messages |
| 6 |
> > > shown below. How to resolve this conflict *safely*? I don't |
| 7 |
> > > want to experiment with fs-related packages :-) |
| 8 |
> > |
| 9 |
> > What worked fine for me: |
| 10 |
> > |
| 11 |
> > emerge --unmerge sys-libs/ss sys-libs/com_err sys-fs/e2fsprogs |
| 12 |
> > emerge --oneshot -v sys-fs/e2fsprogs |
| 13 |
> |
| 14 |
> Why 'oneshot' option is used? |
| 15 |
|
| 16 |
So that you don't record sys-fs/e2fsprogs in the world set. |
| 17 |
|
| 18 |
It's pulled in as a dependency from the system set anyway (that's why |
| 19 |
the --unmerge will tell you that you're unmerging a system package, and that |
| 20 |
you'll potentially break your system), and I personally don't like |
| 21 |
unnecessary packages cluttering up my world set, so I always use --oneshot in |
| 22 |
cases like this. |
| 23 |
|
| 24 |
But, if you leave it out, it does no harm, either. |
| 25 |
|
| 26 |
--- Heiko. |
Archives