emerge blocks after 3.4f x86-64 install and other problems

Anything that pertains to Portage

Moderator: Moderators

Re: emerge blocks after 3.4f x86-64 install and other problems

Postby eris23 » Thu Sep 13, 2007 4:31

1) It's good to know that the missing USE flags are being addressed.
2) As to make.conf, I'll probably reorganize mine and compare yours to see what I can add/change
3) As to masking vs continuous change, again, it would be nice to have a single thread with a "mask this to fix that", or an unchanging url in the wiki

Sabayon may be a month or two behind, but does the overlay allow for a new package.mask,.use,.unmask? It took a while to realize that there were at least two package.mask files to worry about: in /usr/portage/profiles and /etc/portage.

And, why can't Sabayon add by default the lines:
"PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="save"
to make.conf and maybe run mirrorselect on first boot (or, at least give the option).

And, being a user of QEMU, maybe add GCC 3.4.6* to build it (or make it an option like nfs of 3dgames).

Just trying to improve the user experience and streamline things.
eris23
Simple Hen
 
Posts: 66
Joined: Thu Jan 19, 2006 5:53

Re: emerge blocks after 3.4f x86-64 install and other problems

Postby wolfden » Thu Sep 13, 2007 12:51

you can always add your suggestions, but keep in mind, everyone is different
wolfden
Sharecropper
 
Posts: 9050
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Re: emerge blocks after 3.4f x86-64 install and other problems

Postby Necoro » Fri Sep 14, 2007 1:39

eris23 wrote: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.

Meta-Distro based on a Meta-Distro based on a Meta-Distro ... this is sooo meta :cyclopsani:

Sabayon may be a month or two behind, but does the overlay allow for a new package.mask,.use,.unmask?
Yes this is allowed
It took a while to realize that there were at least two package.mask files to worry about: in /usr/portage/profiles and /etc/portage.
:sunny:
Code: Select all
[email protected] sqexpl % locate package.mask | wc -l 
131
ok - not all (read: only some of them) are used by the each system ;)

And, why can't Sabayon add by default the lines:
"PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="save"

The defaults (as per portage-2.1.3) are:
Code: Select all
PORTAGE_ELOG_CLASSES="warn error log"
PORTAGE_ELOG_SYSTEM="echo save_summary

With "echo" introduced, I don't think a normal user wants all output saved seperatly (esp. if you have info in the CLASSES) - thus the defaults should be a choice which are optimal for most users :)
User avatar
Necoro
Advanced Hen
 
Posts: 242
Joined: Mon Apr 23, 2007 22:47
Location: Munich (Germany)

Re: emerge blocks after 3.4f x86-64 install and other problems

Postby eris23 » Fri Sep 14, 2007 7:22

Thanks necoro. I didn't realize that portage had added those lines. I do like the separate summaries for kelogviewer, though.

Another question: are there fundamental conflicts with other overlays? I'm thinking Pro Audio (maybe the KDE or GNOME beta overlays). And, was Sabayon based off the Sunrise overlay?
eris23
Simple Hen
 
Posts: 66
Joined: Thu Jan 19, 2006 5:53

Previous

Return to Portage|Emerge Package Managers

Who is online

Users browsing this forum: No registered users and 0 guests