Well, I just tried something that seems to work,
but has me confused or missing the routine reading
of new portage features.
Anyway upon a routine update (using portage 2.2_rc33
and sets for kde4) I got a message:
All ebuilds that could satisfy =dev-python/sip-4.8.1 have been masked.
One
On Mon, 2009-06-22 at 13:58 +, James wrote:
Well, I just tried something that seems to work,
but has me confused or missing the routine reading
of new portage features.
Anyway upon a routine update (using portage 2.2_rc33
and sets for kde4) I got a message:
All ebuilds that
On Thu, Oct 30, 2008 at 9:12 PM, Jorge Peixoto de Morais Neto
[EMAIL PROTECTED] wrote:
It seems you did not get the point. To attribute a floating point
number to an integer variable is perfectly valid, depending on the
specific program. The compiler normally does not even warn about
this, as
On Thu, Oct 30, 2008 at 9:11 PM, Albert Hopkins [EMAIL PROTECTED] wrote:
I'm coming into this thread kinda late, so feel free to ignore...
... but Jorge is right. This is easily picked up by a lint tool... and
good python programmers use them ;-). Some python-aware editors even
have this
On Wed, Oct 29, 2008 at 10:13 PM, Jorge Peixoto de Morais Neto
[EMAIL PROTECTED] wrote:
The real problem is when you type
float real_number = 4e10;
int integer = real_number;
If your integer can only hold values up to 2^31 - 1 , the behavior of
the above code is undefined.
In a language like
To back myself up:
file name=why_no.py
#!/usr/bin/python
import random
for i in range(1,1):
if random.random() 0.001:
print rare
if malformed beast:
print kick me in the ...
else:
print whatever
/file
To back myself up:
file name=why_no.py
#!/usr/bin/python
import random
for i in range(1,1):
if random.random() 0.001:
print rare
if malformed beast:
print kick me in the ...
else:
print whatever
On Thu, 2008-10-30 at 16:54 -0200, Jorge Peixoto de Morais Neto wrote:
To back myself up:
file name=why_no.py
#!/usr/bin/python
import random
for i in range(1,1):
if random.random() 0.001:
print rare
if malformed beast:
The real problem is when you type
float real_number = 4e10;
int integer = real_number;
If your integer can only hold values up to 2^31 - 1 , the behavior of
the above code is undefined.
In a language like Python, everything either behaves as you intended,
of throws an exception.
This is
On Wednesday 29 October 2008 00:55:42 Jorge Peixoto de Morais Neto wrote:
I mean to really know C,
that is, read a rigorous book such as C: A Reference Manual and be
able to write portable programs with well-defined behavior. Speaking
of well-defined behavior, do you know what happens when
On Wed, Oct 29, 2008 at 3:16 AM, Alan McKinnon [EMAIL PROTECTED] wrote:
On Wednesday 29 October 2008 00:55:42 Jorge Peixoto de Morais Neto wrote:
I mean to really know C,
that is, read a rigorous book such as C: A Reference Manual and be
able to write portable programs with well-defined
I mean to really know C,
that is, read a rigorous book such as C: A Reference Manual and be
able to write portable programs with well-defined behavior. Speaking
of well-defined behavior, do you know what happens when you cast a
float to an int, and the float is too big to fit into the
Hi,
I have
ACCEPT_KEYWORDS=~amd64
in /etc/make.conf
and I want to keep it.
Is it possible to revoke this for whole bunch
of packages like
kde-base/*
I've tried the following line in /etc/portage/package.keywords
kde-base/* -~amd64
but it doesn't help.
Many thanks for a hint,
Helmut
On Tue, 28 Oct 2008 18:07:35 +0100 (CET), Helmut Jarausch wrote:
Is it possible to revoke this for whole bunch
of packages like
kde-base/*
I've tried the following line in /etc/portage/package.keywords
kde-base/* -~amd64
If you are trying to prevent KDE4 installing, it is better to put
On Tue, Oct 28, 2008 at 1:07 PM, Helmut Jarausch
[EMAIL PROTECTED] wrote:
Hi,
I have
ACCEPT_KEYWORDS=~amd64
in /etc/make.conf
and I want to keep it.
Is it possible to revoke this for whole bunch
of packages like
kde-base/*
I've tried the following line in /etc/portage/package.keywords
Andrey Vul wrote:
That looks like it'll only work in paludis. You're going to have to
use shell scripting and output a BFList to package.keywords .
Try $eix -C kde-base --only-names | sed -r 's/$/ -~amd64/' | sudo tee
-a /etc/portage/package.keywords
Don't you guys like (or maybe even know)
On Tue, 28 Oct 2008 15:39:14 -0200, Ricardo Saffi Marques wrote:
Don't you guys like (or maybe even know) autounmask?
Yes, but it unmasks, not masks.
--
Neil Bothwick
Yoda of the Borg am I. Futile, resistance is. Be assimilated, you will.
signature.asc
Description: PGP signature
On Tue, Oct 28, 2008 at 1:39 PM, Ricardo Saffi Marques
[EMAIL PROTECTED] wrote:
Andrey Vul wrote:
That looks like it'll only work in paludis. You're going to have to
use shell scripting and output a BFList to package.keywords .
Try $eix -C kde-base --only-names | sed -r 's/$/ -~amd64/' | sudo
On Tuesday 28 October 2008 22:29:39 Andrey Vul wrote:
On Tue, Oct 28, 2008 at 1:39 PM, Ricardo Saffi Marques
[EMAIL PROTECTED] wrote:
Andrey Vul wrote:
That looks like it'll only work in paludis. You're going to have to
use shell scripting and output a BFList to package.keywords .
Try
Run autounmask, it creates a new file in /etc/portage/package.unmask/
Run a quick awk on it to get it into shape
Move file to /etc/portage/package.mask/
Problem solved in a neat elegant insightful way.
awk? I assumed it was an obsolete language included for compatibility.
People should use
On Tue, 28 Oct 2008 19:34:31 -0200
Jorge Peixoto de Morais Neto [EMAIL PROTECTED] wrote:
Run autounmask, it creates a new file
in /etc/portage/package.unmask/
Run a quick awk on it to get it into shape
Move file to /etc/portage/package.mask/
Problem solved in a neat elegant
On Tuesday 28 October 2008 23:34:31 Jorge Peixoto de Morais Neto wrote:
Run autounmask, it creates a new file in /etc/portage/package.unmask/
Run a quick awk on it to get it into shape
Move file to /etc/portage/package.mask/
Problem solved in a neat elegant insightful way.
awk? I
awk? I assumed it was an obsolete language included for compatibility.
People should use Python, Perl, or sed's s command. Am I wrong?
Yes. You are indeed wrong.
Python and Perl are humungous interpreters that rival Java for size. Perl is
in a class of it's own for syntax bloat.
sed is
On Wednesday 29 October 2008 00:17:50 Jorge Peixoto de Morais Neto wrote:
* Before you ask what, you don't know C?,
A sysadmin doesn't need to know C. It helps to be able to read it of course.
A sysadmin ought to know grep, sed and awk rather well and be quite fluent in
either perl or python,
I mean to really know C,
that is, read a rigorous book such as C: A Reference Manual and be
able to write portable programs with well-defined behavior. Speaking
of well-defined behavior, do you know what happens when you cast a
float to an int, and the float is too big to fit into the int?
Hi!
thanks to all for your replies (and sorry for breaking threat, but I
have you replies in my laptop...).
I finally did an emerge -DNvp.
I'm gonna look for set -o noclobber option.
Cheers and thanks again.
--
Arnau Bria
http://blog.emergetux.net
Wiggum: Dispara a las ruedas Lou.
Lou: eee,
Hi,
due to a human error I've deleted my package.keyowrd file...
(echo package ~x86 /etc/portage/package.keywords)
How may I find which packages were in the file?
I'm afraid of doing an update...
Cheers.
--
Arnau Bria
http://blog.emergetux.net
Wiggum: Dispara a las ruedas Lou.
Lou: eee, es
On 11/27/06, Arnau Bria [EMAIL PROTECTED] wrote:
Hi,
due to a human error I've deleted my package.keyowrd file...
(echo package ~x86 /etc/portage/package.keywords)
How may I find which packages were in the file?
I'm afraid of doing an update...
Option 1:
# emerge -DNvp world
Look for things
On Saturday 10 December 2005 23:07, a tiny voice compelled Brett I. Holcomb to
write:
You say you did it in your home directory but portage looks at /etc/portage
for the files such as package.keywords. Did you move it to /etc/portage?
On Saturday 10 December 2005 22:02, Ernie Schroder wrote:
On Sunday 11 December 2005 14:49, a tiny voice compelled Brett I. Holcomb to
write:
Okay - I figured you did but wasn't sure.
If you have a space before the asterisk it's a problem and it appears you
do - at least in the email.
On Sunday 11 December 2005 11:13, Ernie Schroder wrote:
On
Bump
On Tuesday 06 December 2005 21:33, a tiny voice compelled Ernie Schroder to
write:
After updating to kde-3.5.0, an emerge -up world, as expected wants to
downgrade a whole lot of apps. So, I decided it was time to
get /etc/portage/package.keywords up to date. I did (in my home directory)
You say you did it in your home directory but portage looks at /etc/portage
for the files such as package.keywords. Did you move it to /etc/portage?
On Saturday 10 December 2005 22:02, Ernie Schroder wrote:
Bump
On Tuesday 06 December 2005 21:33, a tiny voice compelled Ernie Schroder to
After updating to kde-3.5.0, an emerge -up world, as expected wants to
downgrade a whole lot of apps. So, I decided it was time to
get /etc/portage/package.keywords up to date. I did (in my home directory)
# equery list | grep kde-base | grep 3.5 package.keywords
and added the ~x86 after the
33 matches
Mail list logo
