Hello, Max!

Thank you VERY much. I'll try it next time! :)
That would work great for me :)

Best regards, Dmitry. 

>(Sorry for the previous e-mail, it seems I forgot to force a text e-mail)
>
>Hi Dmitry,
>
>One way to work around the next emerge sync problem and be able to use 
>your personal tarball is to copy the kernel 2.5.66 ebuild to your 
>PORTDIR_OVERLAY directory.
>
>To do so:
>- Uncomment and set the PORTDIR_OVERLAY in your /etc/make.conf file.
>- Copy the kernel ebuild to 
>/usr/local/portage/sys-kernel/development-sources/ directory. You may 
>need the ChangeLog file, i'm not sure
>- emerge development-sources-2.5.66; it will tell you how to generate 
>the digest file (something like ebuild development-sources-2.5.66 
>digest). Do it.
>- emerge development-sources-2.5.66

>I did not test this directly with the development kernel, but it's a way 
>that I use to bypass the masked packages that I want on my stable 
>machine (actually one of them).

>I personnally have tried to compile the 2.5.66 kernel, but get stuck 
>while compiling the fbdev stuff for the voodoo3 and a cirrus on-board 
>adapter, on a good old P200MMX. I will try to remove these components 
>when I will find some time.
>Max

--
[EMAIL PROTECTED] mailing list

Reply via email to