| 1 |
because a number of other packages want to see /usr/src/linux for the |
| 2 |
running kernel. lm-sensors, vmware, nvidia, ... |
| 3 |
|
| 4 |
I do agree that some effort should be put into fixing the unwanted |
| 5 |
effects that occur when you install another kernel though (haveing to |
| 6 |
reinstall all kernel related packages, and unable to keep already |
| 7 |
installed versions) - I am sure someone must have had a bug against that |
| 8 |
one. |
| 9 |
|
| 10 |
BillK |
| 11 |
|
| 12 |
On Sun, 2003-10-05 at 02:27, Patrick Börjesson wrote: |
| 13 |
> > In theory, Portage could track them if ebuild could be modified to use |
| 14 |
> > /usr/src/pkg when it existed instead of /var/tmp/portage/*/work and |
| 15 |
> > the application was installed via 'ebuild pkg merge'. I'm not sure how |
| 16 |
> > possible that would be for implementation, though. |
| 17 |
> |
| 18 |
> But then the question is: Why? We already have the source unpacked in |
| 19 |
> /var/tmp/portage/*/work so why "move" it to /usr/src? There are already |
| 20 |
> ways for people to do the configure- and make-steps them selves if they |
| 21 |
|
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives