thepld wrote:Wolfden, I've found all of those posts in previous searches, and none addressed any problems I was having.
eris23 wrote:Okay Wolfden, I'll answer your points one by one.
Yes, I've tried leaving make.conf as originally found, and optimized for my Turion64. I've had problems both ways. (CFLAGS="-march=k8 -msse3 -O2 -pipe -fomit-frame-pointer" -- listed at Gentoo as safe).
Yes, I've tried modifying USE flags both per program in the package.use file, and globally in the make.conf. (e.g. gtk, qt3, qemu,etc)
Yes, I haven't stripped out all the unneeded drivers because I'm trying to create a meta-distro optimized for audio/video editing based on Sabayon.
Yes, on a daily basis I edit package.mask, package.unmask, package.use files.
Yes, I search both this forum, gentoo's forums, the various bugzillas, and use google to find other relevant bug fixes.
Yes, I've tried FEATURES="-sandbox" emerge epiphany
Yes, I know these some of these are what one can expect by running bleeding edge (on Debian I tracked incoming, couldn't get a shell at console once, reinstalled to get online, found out that a bash/libreadline update had wiped out the symbolic link to "sh" -- I couldn't figure that one out, I thought it was a library problem)
My feeling is that, as shipped, Sabayon should have USE flags set to be able to build all the included packages.
For instance, libvirt is included, but needs qemu or xen USE flag. The default is neither.
Several packages need the opengl, qt3, qt4 flags set, but it's not a default.
Then there's the issue of blocking packages.
Why can't the Sabayon overlay or something else start with the a package.mask to avoid them. Then a user would at least be able to install security updates.
I tried the smart option to upgrade from 3.4e to 3.4f (with no replace). It hung on virtualbox-bin. I just know it was waiting for the "Yes/No" input, but there was no place to enter it.
Yes, some of these are issues general to Gentoo, but if Sabayon is to become a better distro it should deal with them.
I alternate between emerge, portato, kuroo, equo; dispatch-conf, etc-update, etc. Each has strengths. What's needed is one tool to rule them all.
Users browsing this forum: No registered users and 2 guests