| 1 |
On Thu, Dec 18, 2014 at 07:06:32PM -0500, Harry Putnam wrote: |
| 2 |
|
| 3 |
> Well, that knocks down most of the unwanted pkgs but still as you see: |
| 4 |
> |
| 5 |
> emerge -vp emacs-w3m |
| 6 |
> |
| 7 |
> [ebuild N ] virtual/emacs-24 0 KiB |
| 8 |
> [ebuild N ] virtual/w3m-0 0 KiB |
| 9 |
> [ebuild N ] app-emacs/emacs-w3m-1.4.528_pre20140213 |
| 10 |
> |
| 11 |
> `virtual/emacs-24' still hanging in there |
| 12 |
> |
| 13 |
> I didn't learn enough googling to understand what having that |
| 14 |
> virtual/emacs-24 installed would mean. |
| 15 |
> |
| 16 |
> Would it be possible headaches with emacs-25 installed outside |
| 17 |
> portage. |
| 18 |
> |
| 19 |
> Can anyone say what that package actually does? |
| 20 |
|
| 21 |
It doesn't really do a thing - it only serves as a placeholder for |
| 22 |
functionality that can be provided by a number of different packages |
| 23 |
... or in other words: There are multiple packages that could, in |
| 24 |
theory, provide virtual/emacs-24. app-editors/emacs-24.4-r1 would be |
| 25 |
one of them. |
| 26 |
|
| 27 |
You have told your system by means of package.provided that you have |
| 28 |
installed app-editors/emacs-24, so the system is validly assuming that |
| 29 |
you have something on your system satisfying virtual/emacs-24, and |
| 30 |
thus it shouldn't hurt to let portage install that virtual. |
| 31 |
|
| 32 |
portage(5) has this to say: "Virtual packages (virtual/*) should not |
| 33 |
be specified in package.provided, since virtual packages themselves do |
| 34 |
not provide any files, and package.provided is intended to represent |
| 35 |
packages that do provide files. Depending on the type of virtual, it may |
| 36 |
be necessary to add an entry to the virtuals file and/or add a package that |
| 37 |
satisfies a virtual to package.provided." |
| 38 |
|
| 39 |
Greetings, |
| 40 |
Nils |
Archives