squashfstools ebuild should ask / filter in a way that if the user didnt upgrade to newer kernel (supporting squashfs 3.3) then the user cannot upgrade to squashfstool 3.3. otherwise the user will stuck with old (not compatible) squashfs kernel module and new (not compatible) squashfstools, which will makes the user unable to mount the portage tree created by the new squashfstools (IMHO UGLY). Reproducible: Always Steps to Reproduce: 1.mask kernel > 2.6.22 2.update squashfstools or emerge --update --deep world 3.using the /etc/init.d/squashportage script 4.reboot the system (the script will update the squashed portage tree using the new squashfstools (ver. 3.3) 5.upon reboot cannot mount the new squashfs portage tree image created by the ver 3.3 squashfstools due to old kernel module.
We have no way of knowing what the running kernel is or will be via the package manager. Sorry...
well, can you at leat force the user to update to 2.6.23 kernel by adding rdepend on the ebuild?. or I dont know if this is possible, using uname -r in the ebuild to check?. lastly a big text warning after the emerge done, so the user know if they reboot without new kernel they will got trouble (no portage tree). :>
(In reply to comment #2) > well, can you at leat force the user to update to 2.6.23 kernel by adding > rdepend on the ebuild?. You can only force them to install sources that way. > or I dont know if this is possible, using uname -r in the ebuild to check?. Running `uname -r` in an ebuild is very stupid and will get you stoned to death (figuratively). > lastly a big text warning after the emerge done, so the user know if they > reboot without new kernel they will got trouble (no portage tree). :> No portage tree? Oh noes! The humanity! *cough* emerge sync *cough*
> well, can you at leat force the user to update to 2.6.23 kernel by adding > rdepend on the ebuild?. > You can only force them to install sources that way. At least they can recompile the kernel to solve "no portage tree problems" and if they masked the newer kernel, then the newer squashfs+kernel wont be emerged. > Running `uname -r` in an ebuild is very stupid and will get you stoned to death (figuratively). like doping marijuna or crack? > No portage tree? Oh noes! The humanity! *cough* emerge sync *cough* *achooo* nooo.. how to emerge sync without any tree? *achoo*
(In reply to comment #4) > *achooo* nooo.. how to emerge sync without any tree? *achoo* Uhh, was that a serious question? That's one of the way to get a tree when you first do an install. You don't need an existing tree to use emerge --sync.
>Uhh, was that a serious question? That's one of the way to get a tree when you first do an install. You don't need an existing tree to use emerge --sync. one of my stoned days.....
OK...
I added a note to the ebuild.
