
but they are using the names in the portage tree. why would they want to change them? they are the same as what you see when you emerge things in CLI.patrickbores wrote:This project looks like it has a lot of potential. The only suggestion I'd make at this time is to have more abstract names for categories and sub-categories in the list. That is, "Applications" rather than "app", "Internet" rather than "net", etc...
I have to agree Hayl, that is what the titles are in portage - you do realsie this is using portage right? How could you possibly change the name of the caetgories after an emerge sync?patrickbores wrote:My two cents:
This project looks like it has a lot of potential. The only suggestion I'd make at this time is to have more abstract names for categories and sub-categories in the list. That is, "Applications" rather than "app", "Internet" rather than "net", etc...
A few more abstractions and it could be like a "Click'nCompile'nRun" system (except free)
Patrick
Code: Select all
bash-2.05b# porthole
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Traceback (most recent call last):
File "/usr/bin/porthole", line 40, in ?
import utils
File "/usr/lib/porthole/utils.py", line 44, in ?
import gtk, portagelib
File "/usr/lib/python2.3/site-packages/gtk-2.0/gtk/__init__.py", line 43, in ?
from _gtk import *
RuntimeError: could not open display

Uh, because what good is a GUI tool if it's not high-level enough to offer something beyond what you get from the CLI?but they are using the names in the portage tree. why would they want to change them? they are the same as what you see when you emerge things in CLI.
We have discussed this. While it is certainly feasible, my personal feeling is that it would be a distraction for people who mainly use Porthole for browsing and searching the portage tree.patrickbores wrote:The only suggestion I'd make at this time is to have more abstract names for categories and sub-categories in the list. That is, "Applications" rather than "app", "Internet" rather than "net", etc...
Can you run other X apps as root?calhoun wrote:When I try to run it as root, I get the following error:Code: Select all
Xlib: connection to ":0.0" refused by server

I reckon that if more metadata was added to the portage tree, this would be very feasible, and perhaps even recommended. But, for now, there's little point. And of course, if such a thing is implemented, you'd have to allow people to switch between the two styles.far wrote:We have discussed this. While it is certainly feasible, my personal feeling is that it would be a distraction for people who mainly use Porthole for browsing and searching the portage tree.patrickbores wrote:The only suggestion I'd make at this time is to have more abstract names for categories and sub-categories in the list. That is, "Applications" rather than "app", "Internet" rather than "net", etc...
Code: Select all
xhost +local:Well thought out! Now that you point it out, it has only seg faulted and disappeared when on a desktop I have not been using - Yep, just done it again when finished a compile on a desk3 while I was on desk2. Let me know if you need any more info. HTHdol-sen wrote:We just got a bug report that says the segfaults are occuring when porthole does not have focus when emerge completes and the main porthole window gets the callback signal to reload the databases.
If you are having any problems with segfaults. Can you confirm this, and if need be make sure that porthole is selected as the active window to prevent the segfaults.
This may be the clue we needed to figure out why they happened.
I may postpone the impending release of porthole-0.3.1 if we can eliminate this bug.
Thanks,
Thanks alot ugly_orc, that worked perfectly.ugly_orc wrote:Personnaly, in order to run X apps as root, I need to runbefore su'ing to root. This line can also be run automatically by puting it in ~/.bash_profile or something like that.Code: Select all
xhost +local:
After that, porthole works just fine as root!
Far, personally I prefer not to run applications as root unless they really need it, like emerge or porthole in this case. Its probably not even an application i will run because I prefer to run "emerge sync", "emerge system" and "emerge world"..... I'm still fairly new to Gentoo as of November (new but not that new) so I'm playing with anything that interests me.far wrote:You are supposed to be able to run X apps as root. I don't know how you have managed to make it not work.calhoun wrote:So how is this application usable? Am I missing something in the setup?
I understand perfectly and I do the same myself.calhoun wrote:Far, personally I prefer not to run applications as root unless they really need it, like emerge or porthole in this case. Its probably not even an application i will run because I prefer to run "emerge sync", "emerge system" and "emerge world".....
Yes I am a maintainer, but I don't think Porthole should meddle with the X setup. I don't know how to check if root is allowed to connect to the X server either.calhoun wrote:I'm not sure if your on the development team or not, but since this app has the requirement to be run as root, maybe during the emerge process a check could be put in to verify that applications can be run as root. Or maybe that the above "xhost +local:" blurb is in the bash profile. Having not programmed in about 15 years, I'm not sure what the clean way is to check this.

