| 1 |
On Saturday 04 October 2003 12:56, Luke-Jr wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> On Saturday 04 October 2003 02:25 am, Jon Portnoy wrote: |
| 6 |
> > You're not suggesting anything that provides a tangible benefit, you're |
| 7 |
> > just suggesting expanding our tree to do something we already do. That |
| 8 |
> > doesn't make sense. |
| 9 |
> |
| 10 |
> As it is currently done, Portage cannot track the kernel itself, only the |
| 11 |
> kernel sources. Also, it leaves the kernel in /usr/src/linux when it isn't |
| 12 |
> really needed once installed except perhaps to save configuration (which |
| 13 |
> genkernel has stuff for) and object files to speed future compilations |
| 14 |
> (which Portage should do if you keep /var/tmp/portage around anyway). |
| 15 |
> It makes little sense to compile and install other packages but not compile |
| 16 |
> and install Linux itself. |
| 17 |
|
| 18 |
Agreed. (My other post was written and sent to my local server before reading |
| 19 |
yours but took a while to get out) |
| 20 |
|
| 21 |
However, having portage compile and install Linux has several issues. Portage |
| 22 |
would need to be able to: |
| 23 |
1) handle multiple saved configurations automatically. |
| 24 |
2) update lilo/grub automatically _with_ backup. |
| 25 |
3) extract the source to /usr/src if need be (as already mentioned) |
| 26 |
4) handle different configurations of the same kernel version. |
| 27 |
|
| 28 |
Tangible benefits that I can see: |
| 29 |
1) ccache can be used in compiling the kernel automatically |
| 30 |
2) a lot of disk space can be saved. |
| 31 |
|
| 32 |
A lot of work would need to be done to do this successfully, though; maybe |
| 33 |
something that should be left for portage v3... |
| 34 |
|
| 35 |
Jason |
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives