| 1 |
On Thursday 07 May 2009 21:07:57 maxim wexler wrote: |
| 2 |
> > > Whatever portage is fetching is turning into something |
| 3 |
> > |
| 4 |
> > I didn't order. I checked in distfiles and sure enough, |
| 5 |
> > there's no klibc* but a growing linux-2.6.26.tar.bz2. |
| 6 |
> > Weird. |
| 7 |
> > |
| 8 |
> > Nothing is wrong. That file is required for klibc. From the |
| 9 |
> > ebuild notes: |
| 10 |
> |
| 11 |
> Yes, I saw that too, but |
| 12 |
> |
| 13 |
> 1) why doesn't it list it from the start? |
| 14 |
|
| 15 |
Q: How many packages have you ever installed that have multiple SRC_URIs and |
| 16 |
portage has given you a list of them up front? |
| 17 |
|
| 18 |
A: None. You need "emerge -pvf" for that |
| 19 |
|
| 20 |
> 2) the 2.6.28 source is already in my box, and it wants the 26? |
| 21 |
|
| 22 |
Read the ebuild notes. It fetches 26 because the ebuild says it must fetch 26, |
| 23 |
not any old version you feel like. |
| 24 |
|
| 25 |
Why 26 specifically? Well, headers can change between versions. Obviously, |
| 26 |
either a) the developer's code will only build against that particular version |
| 27 |
or b) the developer feels that's the safest version. |
| 28 |
|
| 29 |
It's all right there in the notes - the very ones you chose the snip out of |
| 30 |
your reply...... |
| 31 |
|
| 32 |
-- |
| 33 |
alan dot mckinnon at gmail dot com |
Archives