Re: [gentoo-user] Laptop Lid Close...

2009-01-25 Thread Gian Calgeer
Hi

BRM wrote:

 I mostly run KDE 3.5 (I'll go to KDE4 when I can...once portage 2.2 comes
 out and all)

There's no need to wait for Portage 2.2 in order to install KDE 4, 2.1.6.4
also seems to support EAPI 2. 

Gian




Re: [gentoo-user] chrome and everything

2011-06-02 Thread Gian Calgeer

On 02.06.2011 13:42, Jesús J. Guerrero Botella wrote:

I don't have spare time for philosophical stuff (and it's not amongst
my insterests anyway). But, you can always use some extension to block
flash contents. Then you click only in the flashes you want to see.
That will probably help to narrow down the scope of the problem. So,
try adblock and flashblock. The extra ram they will suck probably
worths the trouble.
There's no need for an extension to get that behaviour with Chromium. 
You can simply enable click to play on the about:flags page, then 
choose click to play for plugins in the content settings of Chromium.




[gentoo-user] emerge --autounmask-write: specify file

2011-07-05 Thread Gian Calgeer

Hi

I was really looking forward to the new autounmask feature in portage, 
as it replaces my ugly home-grown bash script. However, it just picks a 
seemingly random file in /etc/portage/package.keywords to put things 
into. Is there a way to specify which file it writes things into? 
Ideally, I would like to have file names based on the package I'm 
emerging, so if e.g. I do emerge --autounmask-write=y 
dev-ruby/rest-client, it should put the keywords into 
/etc/portage/package.keywords/dev-ruby-rest-client or similar. 
Alternatively, it would be great if I could at least get portage to 
output the keywords to stdout without mixing it up with other output, so 
I could redirect it to a file I want. Is there any way to do this?


Gian



Re: [gentoo-user] emerge --autounmask-write: specify file

2011-07-06 Thread Gian Calgeer

On 05.07.2011 17:58, Dale wrote:
I was using autounmask to do this and it does just like you want.  
However, the last time I used autounmask, it was different.  You may 
want to try that tho to see if it helps in some way.


The feature with emerge picks the first file I think in the 
directory.  It is annoying as heck for sure.  Since it is a work in 
progress, maybe they will change this weird behavior soon.


Then again, that is yet another option to have to remember too.  Jeez.

Dale

:-)  :-)
Thanks for the hint. Last time I tried it, it had problems (not removing 
files when the unmasking didn't succeed or something like that, I don't 
remember exactly). However, maybe things have changed for the better.