gperiodic rxvt-unicode unipath pekwm

General talk about packaging procedures and packages.
Post Reply
User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 21. Sep 2012, 12:41

I thought I'd do these next - please let me know of any reason not to!
Last edited by mimosa on 14. Oct 2012, 11:39, edited 1 time in total.

User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 27. Sep 2012, 20:10

pekwm is about to release a new version, so I'm holding off on that one. But I've submitted the other three.

User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 4. Oct 2012, 17:59

I'm just building pekwm now (never mind waiting for RC to become R).

I must say the Gilouche theme Gapan packaged it with last time is quite seductive!

User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 5. Oct 2012, 18:08

pekwm's nearly ready to go but I just need to update the menu. As far as I can see that means:

LibreOffice instead of OO
engrampa instead of file-roller
atril instead of evince
xfburn instead of brasero

... the last three taken from the original announcment of the alpha.

Anything else that springs to mind? Is gksu still alright?

Also, can engrampa and atril be called as such (exec path, not menu entry), or is it better to use their boring mate-hyphenated-generic-names? Presumably the idea is that if anyone ever notices that "atril" is an ugly name, and changes it, config files and such needn't be altered.

EDIT And what about gtk*setup?

I think I'll build this and submit with the proviso that the menu is a WIP; it'll be easy enough to change when the answers to these questions have become clear.

EDIT2

However, even "Terminal" doesn't work. Investigstion reveals that $TERM is called, but that variable appears to be defined as 'Linux' [???]
What about something like:

Code: Select all

exec xterm || exec $TERM
?

User avatar
gapan
Salix Wizard
Posts: 5528
Joined: 6. Jun 2009, 17:40

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by gapan » 6. Oct 2012, 13:38

mimosa wrote:Anything else that springs to mind? Is gksu still alright?
yes, gksu is fine.
mimosa wrote:Also, can engrampa and atril be called as such (exec path, not menu entry), or is it better to use their boring mate-hyphenated-generic-names? Presumably the idea is that if anyone ever notices that "atril" is an ugly name, and changes it, config files and such needn't be altered.
Use whatever you like, really.
mimosa wrote:EDIT And what about gtk*setup?
what about them?
mimosa wrote:However, even "Terminal" doesn't work. Investigstion reveals that $TERM is called, but that variable appears to be defined as 'Linux' [???]
What about something like:

Code: Select all

exec xterm || exec $TERM
?
I don't understand what you're trying to do. $TERM is not a variable that points to a terminal emulator app, as you think it does. It is a variable that tells a terminal emulator app what features to use.
Image
Image

User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 6. Oct 2012, 14:29

Thanks gapan. One problem solved, I think. Here is the first entry in the pekwm menu in the 13.37 package:

Code: Select all

Entry = "Terminal" { Actions = "Exec $TERM &" }
... and I see that before that there is

Code: Select all

# Variables
INCLUDE = "vars"
... and the vars file has one entry:

Code: Select all

vanilla[.pekwm]$ cat vars | less
$TERM="xterm"
lines 1-1/1 (END
... so probably 'vars' needs fixing or copying somewhere.

gtk*setup, I just wondered if it might have changed, don't know why. So no.

One final thing. When I run my package in 13.37 Ratpoison, the background is a black that goes very nicely indeed with the theme. But in current, it's a boring grey. Maybe this is some config left over in Ratpoison (where I do the preparatory work for my packages). But I like it much better than the grey.

Can you remember if when you packaged it, it was supposed to be black or grey? And off the top of your head, where to set this? Is it actually part of the gilouche theme? If you don't remember, I'll investigate.

User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 6. Oct 2012, 17:04

In fact the problem with the terminal is that xterm isn't installed in the beta. Should I make it a dependency of the package, or do something more complex to make pekwm compatible with all Salix editions?

At the moment I'm trying to set the black background using feh (in .xinitrc). There has to be an easier way though.

User avatar
gapan
Salix Wizard
Posts: 5528
Joined: 6. Jun 2009, 17:40

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by gapan » 6. Oct 2012, 17:50

mimosa wrote:Thanks gapan. One problem solved, I think. Here is the first entry in the pekwm menu in the 13.37 package:

Code: Select all

Entry = "Terminal" { Actions = "Exec $TERM &" }
... and I see that before that there is

Code: Select all

# Variables
INCLUDE = "vars"
... and the vars file has one entry:

Code: Select all

vanilla[.pekwm]$ cat vars | less
$TERM="xterm"
lines 1-1/1 (END
... so probably 'vars' needs fixing or copying somewhere.
No, it seems $TERM is being overridden in pekwm somehow. I wouldn't worry about it much. Nobody said everything in the menu should be working out of the box with pekwm. The way pekwm works with static menus, it's impossible to cover all cases anyway.

mimosa wrote:One final thing. When I run my package in 13.37 Ratpoison, the background is a black that goes very nicely indeed with the theme. But in current, it's a boring grey. Maybe this is some config left over in Ratpoison (where I do the preparatory work for my packages). But I like it much better than the grey.

Can you remember if when you packaged it, it was supposed to be black or grey? And off the top of your head, where to set this? Is it actually part of the gilouche theme? If you don't remember, I'll investigate.
I don't really remember and it doesn't really matter in my opinion.
mimosa wrote:In fact the problem with the terminal is that xterm isn't installed in the beta. Should I make it a dependency of the package, or do something more complex to make pekwm compatible with all Salix editions?
No, just leave it as it is. If someone installs pekwm, he should be expected to edit some of the menus anyway.
mimosa wrote:At the moment I'm trying to set the black background using feh (in .xinitrc). There has to be an easier way though.
Don't do that either. How do you know feh is going to be installed?
Image
Image

User avatar
mimosa
Salix Warrior
Posts: 3096
Joined: 25. May 2010, 17:02
Contact:

Re: [WIP] gperiodic rxvt-unicode unipath pekwm

Post by mimosa » 6. Oct 2012, 19:01

I was going to make feh a dependency too; but I expect there's an easier and more elegant way. I tried with xsetroot, and maybe I should have another go.

However, you're right, I'm worrying too much about things anyone likely to want to use this will know how to fix (or find out).

I do really like the black background with gilouche though.

EDIT

Code: Select all

xsetroot -solid black 
does it.

Post Reply