Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
aewm++
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
kevev
n00b
n00b


Joined: 05 Jan 2005
Posts: 42
Location: Tejas

PostPosted: Wed Jan 05, 2005 8:17 am    Post subject: aewm++ Reply with quote

anyone tried installing aewm++ on 2004.3? Its masked. when unmasking it I get

(masked by: missing keyword)

Is there a string to get me passed this? maby ignore string?


Ohh..ya! I love Gentoo. Im learning and I hate Redhat! (again :P )
_________________
your only as smart as the Computer doing your thinking.
Back to top
View user's profile Send private message
ruben
Guru
Guru


Joined: 04 Jul 2003
Posts: 462

PostPosted: Wed Jan 05, 2005 9:09 am    Post subject: Reply with quote

You can try it by changing the ebuild. The ebuild is in a directory like "/usr/portage/x11-wm/aewm/aewm....ebuild or something like that (can't check right now). In that file you will see a line like:
Code:
KEYWORDS="x86"

change that to the following:
Code:
KEYWORDS="x86 ppc"

Then you will be able to emerge it and see whether it works. Notice that the ebulid will be restored to the original version after an "emerge sync".

In case it works, let the developers know and ask them to add the "ppc" keyword. Either use bugs.gentoo.org or mail to gntoo-ppc-dev@lists.gentoo.org
Back to top
View user's profile Send private message
gnomeza
Tux's lil' helper
Tux's lil' helper


Joined: 31 Dec 2003
Posts: 97

PostPosted: Wed Jan 05, 2005 2:18 pm    Post subject: Reply with quote

Using the command

Code:

ACCEPT_KEYWORDS="x86" emerge aewm


is easier than editing the ebuild itself.
Back to top
View user's profile Send private message
zeekec
n00b
n00b


Joined: 24 Feb 2004
Posts: 56
Location: Athens, GA, USA

PostPosted: Wed Jan 05, 2005 2:29 pm    Post subject: Even better. Reply with quote

Edit /etc/portage/package.keyword and add the apropriate keyword to the atom.
Code:
x11-wm/aewm++ ~x86


This is the currently recommended method.
The other two methods will work, but the first will get overwritten by an emerge sync and the second won't keep the package updated.

Erik

P.S. That should be:
Code:
x11-wm/aewm++ x86

_________________
Against stupidity the very gods
Themselves contend in vain.
-Johann Christoph Friedrich von Schiller (1801)


Last edited by zeekec on Wed Jan 05, 2005 3:42 pm; edited 1 time in total
Back to top
View user's profile Send private message
ruben
Guru
Guru


Joined: 04 Jul 2003
Posts: 462

PostPosted: Wed Jan 05, 2005 3:01 pm    Post subject: Reply with quote

@gnomeza:

Your method is not recommended. It is easier, yes.... but it will also pull in all dependencies of aewm++ with the "x86" keyword, instead of with the "ppc" keyword. This can lead to some troubles later on (like downgrading of libraries....).

@ zeekec:

In case i may assume you meant "~ppc" instead of "~x86": your method will not work, since aewm is masked by missing keyword. The original poster mentioned he already unmasked it (which means, i assume, that he did what you proposed with "~ppc"). On the other hand, if you did mean "~x86": i would definitely never add the line you propose with "~x86" on a *ppc* system.
Back to top
View user's profile Send private message
zeekec
n00b
n00b


Joined: 24 Feb 2004
Posts: 56
Location: Athens, GA, USA

PostPosted: Wed Jan 05, 2005 3:28 pm    Post subject: Reply with quote

ruben wrote:

In case i may assume you meant "~ppc" instead of "~x86": your method will not work, since aewm is masked by missing keyword. The original poster mentioned he already unmasked it (which means, i assume, that he did what you proposed with "~ppc"). On the other hand, if you did mean "~x86": i would definitely never add the line you propose with "~x86" on a *ppc* system.


If the package has the ~ppc keyword then adding ~ppc will work, but aewm++ only has ~amd64 and x86. Adding ~ppc will not fix the keyword problem. (Although it might be fun to use ~amd64.)

I believe that package.keyword woks the same as ACCEPT_KEYWORDS.

I must admit I not entirely sure how this effects the dependencies of aewm++, but I have keyworded packages using this method. I don't recall the exact packages, but I do recall that it allowed me to install and use them. If I recall correctly, it was some encryption packages for Kmail.

Erik

Some more information can be found at (but it only mentions mixing ~x86 and x86):
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
_________________
Against stupidity the very gods
Themselves contend in vain.
-Johann Christoph Friedrich von Schiller (1801)
Back to top
View user's profile Send private message
zeekec
n00b
n00b


Joined: 24 Feb 2004
Posts: 56
Location: Athens, GA, USA

PostPosted: Wed Jan 05, 2005 3:34 pm    Post subject: pekwm Reply with quote

Kevev,

Perhaps you should try pekwm. It's ebuild is keyworded ppc.

Erik
_________________
Against stupidity the very gods
Themselves contend in vain.
-Johann Christoph Friedrich von Schiller (1801)
Back to top
View user's profile Send private message
ruben
Guru
Guru


Joined: 04 Jul 2003
Posts: 462

PostPosted: Wed Jan 05, 2005 4:02 pm    Post subject: Reply with quote

zeekec wrote:
I believe that package.keyword woks the same as ACCEPT_KEYWORDS.

I must admit I not entirely sure how this effects the dependencies of aewm++, but I have keyworded packages using this method. I don't recall the exact packages, but I do recall that it allowed me to install and use them. If I recall correctly, it was some encryption packages for Kmail.

Using package.keywords is the right way for emerging packages when you want the (unstable) "~ppc" version instead of the (stable) "ppc" version.

The difference with ACCEPT_KEYWORDS is probably clear with an example. Suppose i have package X which has as a dependency package Y. If i want the unstable version for X, i can just add a line to package.keywords for package X (with "~ppc"). As a result, when i emerge X, i will get the unstable version for X and the stable version for package Y. If i use ACCEPT_KEYWORDS, however, i will get the unstable version of package X but also the unstable version of the dependency, package Y.

In general, the use of ACCEPT_KEYWORDS should be avoided, because then portage doesn't know for which packages you want the unstable version, and so, when you update your system with something like:
Code:
emerge -uDav world
portage will propose to downgrade the unstable packages you emerged with ACCEPT_KEYWORDS to their stable version.

What you say, is right. Using package.keywords for mixing software branches is fine if you stick to the same architecture: mixing "x86" and "~x86", or mixing "ppc" and "~ppc". But i think it's not a good idea to mix "ppc" with "~x86".
Back to top
View user's profile Send private message
zeekec
n00b
n00b


Joined: 24 Feb 2004
Posts: 56
Location: Athens, GA, USA

PostPosted: Wed Jan 05, 2005 4:30 pm    Post subject: Reply with quote

ruben wrote:
In general, the use of ACCEPT_KEYWORDS should be avoided, because then portage doesn't know for which packages you want the unstable version, and so, when you update your system with something like:
Code:
emerge -uDav world
portage will propose to downgrade the unstable packages you emerged with ACCEPT_KEYWORDS to their stable version.

What you say, is right. Using package.keywords for mixing software branches is fine if you stick to the same architecture: mixing "x86" and "~x86", or mixing "ppc" and "~ppc". But i think it's not a good idea to mix "ppc" with "~x86".


Ruben,

Your first point is why I suggested using the package.keyword file. (Note: If the dependencies are keyworded, they would have to be added as well.)

On your second point I also agree, but (You knew that was coming.) some packages will work fine on a ppc that aren't even keyworded to ~ppc. There just hasn't been enough testing (or any). If these packages are going to be tested, someone is going to have to accept an x86 keyword at some point (and more power to them).

If kevev is willing to unmask a package, he's probably willing to go the rest of the way and keyword it as well and be our alpha tester.

Erik
_________________
Against stupidity the very gods
Themselves contend in vain.
-Johann Christoph Friedrich von Schiller (1801)
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Jan 05, 2005 9:23 pm    Post subject: Reply with quote

To clear things up here:

Do not use the x86 keyword on ppc machines. Even if it works in some cases, as Ruben suggests, it will emerge the dependencies as well with the x86 keyword. There are cases where ebuilds differentiate between the arches for applying patches or using binaries from the specific arch in the keywords.

The best way to do this is to create a portage overlay directory. This can be done by uncommenting the PORTDIR_OVERLAY variable in make.conf. You then copy the ebuild along with its related files to the overlay and add your keyword to the ebuild in the overlay. This will allow the ebuild to be preserved over an emerge sync and will let you use the ppc keyword to emerge the ebuild. If you just want to test the package to see if it works, you can edit the ebuild in the tree (emerge gentoolkit-dev and try ekeyword, it's easier than editing by hand) and if it works, copy the ebuild to your overlay.

After you've tested the ebuild with the ppc keyword, please make a bug in bugzilla for the package so we (the ppc developers) can add the keyword.

Thanks!
Back to top
View user's profile Send private message
kevev
n00b
n00b


Joined: 05 Jan 2005
Posts: 42
Location: Tejas

PostPosted: Thu Jan 06, 2005 4:00 am    Post subject: crap Reply with quote

no workie. :(

gives error:

windowmanager.cc:628: error: ISO C++ forbids cast to non-reference type used as lvalue
make: *** [windowmanager.o] Error 1

thanks for the responses. If you guys want me to keep trying I could use some input. I may try the wm mentioned by zeekec.
_________________
your only as smart as the Computer doing your thinking.
Back to top
View user's profile Send private message
SnEptUne
l33t
l33t


Joined: 23 Aug 2004
Posts: 653

PostPosted: Thu Jan 06, 2005 8:49 am    Post subject: Reply with quote

Both x11-wm/aewm-1.2.3 and x11-wm/aewm++-1.0.24 compile fine on my ppc (PPC9600 Oldworld).

Code:
mail / # cat /proc/cpuinfo
processor       : 0
cpu             : 604ev
clock           : 300MHz
revision        : 1.0 (pvr 000a 0100)
bogomips        : 299.00
machine         : Power Macintosh
motherboard     : AAPL,9500 MacRISC
detected as     : 16 (PowerMac 9500/9600)
pmac flags      : 00000000
L2 cache        : 256K unified
memory          : 512MB
pmac-generation : OldWorld


I am using gcc version 3.3.3 (Gentoo Linux 3.3.3_pre20040408-r1) with nptl support.
_________________
"There will be more joy in heaven over the tear-bathed face of a repentant sinner than over the white robes of a hundred just men." (LM, 114)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum