Puppy Linux Discussion Forum

Sofiya wrote: ↑Mon May 29, 2023 12:16 pm

everything is very simple open pamac
in the search enter xfe - select it
then click build , wait for pamac to build the package then install

I tried that last night, but I didn't get any results for Xfe, so I came to the conclusion that I need to download the AUR package to a specific location in the system first before it will show up in the pacmac gui.

That raised the question of whether I should download the 'snapshot' package from the AUR or if it was better to get the github code. I don't use github much but I do have an account.

Last night I downloaded the 'snapshot' package. but I didn't know where to put it.

geo_c wrote: ↑Mon May 29, 2023 12:21 pm

Sofiya wrote: ↑Mon May 29, 2023 12:16 pm

everything is very simple open pamac
in the search enter xfe - select it
then click build , wait for pamac to build the package then install

I tried that last night, but I didn't get any results for Xfe, so I came to the conclusion that I need to download the AUR package to a specific location in the system first before it will show up in the pacmac gui.

That raised the question of whether I should download the 'snapshot' package from the AUR or if it was better to get the github code. I don't use github much but I do have an account.

Last night I downloaded the 'snapshot' package. but I didn't know where to put it.

pamac will do everything himself
But first you have to install pacman -S --needed base-devel

pacman -S --needed base-devel
--needed we specify so that we do not reinstall those packages that are already installed

@Sofiya

I installed a few things from the >Menu>System>Add/Remove Software, like Ranger, Midnight Commander, Frescobaldi, lilypond.

All went smoothly, but I'm not sure I'm seeing packages from AUR. I notice your screenshot has a category for AUR, but mine isn't showing it. And a search for Xfe yields no results. I know I could use the package you provided earlier, but I'm trying to figure out how to use the manager correctly myself.

I ran pacman -S --needed base-devel again to be sure, which returned that it's already installed, and trying to run pacmac update returns pacmac command not found.

I'm sure I'm missing something obvious.

BTW, everything about this system is super nice! The utilities are slick, it runs fast, and looks great.

@Sofiya

Uh......yeah

The obvious command not found blind spot is that I'm trying pacmac instead of pamac

I don't have an eye for detail, dangerous character flaw in the computer world.

geo_c wrote: ↑Mon May 29, 2023 1:57 pm

@Sofiya

I installed a few things from the >Menu>System>Add/Remove Software, like Ranger, Midnight Commander, Frescobaldi, lilypond.

All went smoothly, but I'm not sure I'm seeing packages from AUR. I notice your screenshot has a category for AUR, but mine isn't showing it. And a search for Xfe yields no results. I know I could use the package you provided earlier, but I'm trying to figure out how to use the manager correctly myself.

I ran pacman -S --needed base-devel again to be sure, which returned that it's already installed, and trying to run pacmac update returns pacmac command not found.

I'm sure I'm missing something obvious.

BTW, everything about this system is super nice! The utilities are slick, it runs fast, and looks great.

pacmac does not have such a command, there is a pamac command

Have you enabled support for AUR packages in Pamac?
in pamac settings > third party set the switch to ON

Okay, I installed Xfe using command line: pamac build xfe

Sorry to waste your energies!

Sofiya wrote: ↑Mon May 29, 2023 2:12 pm

Have you enabled support for AUR packages in Pamac?
in pamac settings > third party set the switch to ON

Thanks, I had NOT done that! I did now.

I think I'm set. I appreciate all your efforts to help!

geo_c wrote: ↑Mon May 29, 2023 2:17 pm

Sofiya wrote: ↑Mon May 29, 2023 2:12 pm

Have you enabled support for AUR packages in Pamac?
in pamac settings > third party set the switch to ON

Thanks, I had NOT done that! I did now.

I think I'm set. I appreciate all your efforts to help!

View installed packages from the AUR
open Pamac - Installed > Foreign

you can save packages you install from the AUR by setting the switch to ON

Also clear build cache

built packages are stored in /var/cache/private/pamac if i remember exactly
before cleaning, you can save them for later installation

pacmac update returns pacmac command not found

One day they will implement same as Google does "did you mean ..."
pacmac update
Did you mean pacman ? Try again!
snapmac update
Did you mean snap ? Try again!
pkgman update
What did you mean ? Try again!
pacsnack update
Go away! You are driving me nuts!

Actually Arch is not as difficult as it seems. maybe because I've been with LInux for over 16 years. For me, the Puppy was a curiosity

Sofiya wrote: ↑Mon May 29, 2023 3:12 pm

Actually Arch is not as difficult as it seems. maybe because I've been with LInux for over 16 years. For me, the Puppy was a curiosity

I think anything that's new for someone can easily be experienced as difficult, that's human nature IMO. Just gotta get used to it, so then it's not "new" anymore.

fredx181 wrote: ↑Mon May 29, 2023 3:29 pm

Sofiya wrote: ↑Mon May 29, 2023 3:12 pm

Actually Arch is not as difficult as it seems. maybe because I've been with LInux for over 16 years. For me, the Puppy was a curiosity

I think anything that's new for someone can easily be experienced as difficult, that's human nature IMO. Just gotta get used to it, so then it's not "new" anymore.

I agree, this also requires a desire to learn, and not as some are used to (everything should be out of the box)
if you judge, too, the box was once created by someone and continues to be supported

fredx181 wrote: ↑Mon May 29, 2023 3:29 pm

Sofiya wrote: ↑Mon May 29, 2023 3:12 pm

Actually Arch is not as difficult as it seems. maybe because I've been with LInux for over 16 years. For me, the Puppy was a curiosity

I think anything that's new for someone can easily be experienced as difficult, that's human nature IMO. Just gotta get used to it, so then it's not "new" anymore.

By the way, I went to the forum for the first time and after looking through all the Puppies, my eyes fell on UbuntuDogs. I was immediately attracted by the beautiful design and the presence of the Synaptic package manager. Puppy Fosapup64 was installed later. Since my very first exposure to Linux started with Linux Mint xx.x in 2002

Sofiya wrote: ↑Mon May 29, 2023 3:57 pm

By the way, I went to the forum for the first time and after looking through all the Puppies, my eyes fell on UbuntuDogs. I was immediately attracted by the beautiful design and the presence of the Synaptic package manager. Puppy Fosapup64 was installed later. Since my very first exposure to Linux started with Linux Mint xx.x in 2002

For me I only tried one full install of Ubuntu back in 2007-08 or so, gave up on it as being a cheap sort of windows OS, then tried a couple linux audio distros with live CDs, and then I stumbled on the puppy forum and downloaded 4.31, and soon after Lucid puppy. I was hooked. Fast lean and easy to install.

So I never had any real experience with linux/unix except for puppy-linux. Although it did help that my dad was an IBM software engineer in the 60s and 70s, had early kit/built personal computers like the SWTP 6800, and the first PCXT which I grew up playing with. So I was comfortable with text based command line interfaces, and the idea of "batch files."

But many things I take for granted as being 'linux' are in fact 'puppy-linux' like the /mnt/home symlink and such.

I was shocked recently even to discover that most of the right-click utilities in Rox were not native to Rox at all, but puppy-linux developed.

I've always been sold on the portable/reproducible aspect of puppies, dogs, and now kennel-linuxes. No other mainstream OS is quite so versatile.

It has amazed how many newbies this year have come in with the assumption that they need to format a dedicated partion to install. I only have two per drive, a grub partition and one full of OS's.

It's hard to go back to the 'full install' mentality. And thankfully, no need to.

I learned on IBM mainframes and Digital Corp PDP-11/70 's
Built computer kit ALTAIR 680B using a teletype and paper tape reader to bootstrap load TinyBasic and a an assembler
I use a 512 mb partition for the boot loader and the the rest is a second partition formatted as ext4 which holds many many Puppy Linux's of all breeds and Kennel Linux and some FirstRib creations all living on the samex one partition.

I do all my machines in as similar fashion. Or I boot from a USB drive of some sort when using a machine that has no HDD of it;s own and no battery for example. Right now using a gaming computer being thrown out but has a nice GPU so decided to see if the machine works as is......booted KLV-Airedale-rc17 and everything works....graphics through the GPU and sound as well.

This machine booted Windows 10 and the fans went nuts.........running KLV all is quite on the western front.

KLA Session Control

/usr/local/bin/kla-shutdown

#!/bin/sh
## KLA Session Control
## Sofiya 2023
## To change the banner, change the name " logout-banner.gif " in the code line ( <input file>/usr/share/pixmaps/kla-session/logout-banner.gif</input>  ) 
## The banners are in  /usr/share/pixmaps/kla-session/

export TEXTDOMAIN=kla-shutdown
export OUTPUT_CHARSET=UTF-8

export shutdown=" 
<window title=\"$(gettext 'KLA Session Control')\" icon-name=\"gtk-preferences\">
  <vbox>
  <pixmap>
     <input file>/usr/share/pixmaps/kla-session/logout-banner.gif</input> 
  </pixmap> 
  
  
  <hbox homogeneous=\"true\">
  <button tooltip-text=\" $(gettext 'Powerdown the computer') \" use-underline=\"true\" width-request=\"120\" theme-icon-size=\"24\">
  <label>$(gettext 'Powerdown')</label>
  <input file icon=\"system-shutdown\"></input>
  <action>systemctl poweroff &</action>
  <action type=\"exit\">Exit</action>
  </button>
  <button tooltip-text=\" $(gettext 'Suspend the computer') \" use-underline=\"true\" width-request=\"120\" theme-icon-size=\"24\">
  <label>$(gettext 'Suspend')</label>
  <input file icon=\"system-suspend\"></input>
  <action>systemctl suspend &</action>
  </button>
  <button tooltip-text=\" $(gettext 'Reboot the computer') \" use-underline=\"true\" width-request=\"120\" theme-icon-size=\"24\">
  <label>$(gettext 'Reboot')</label>
  <input file icon=\"system-reboot\"></input>
  <action>systemctl reboot &</action>
  <action type=\"exit\">Exit</action>
  </button>
  </hbox>
  <hbox homogeneous=\"true\">
  <button tooltip-text=\" $(gettext 'Restart the window manager') \" use-underline=\"true\" width-request=\"120\" theme-icon-size=\"24\">
  <label>$(gettext 'Restart WM')</label>
  <input file icon=\"system-switch-user\"></input>
  <action>openbox --restart &</action>
  </button>
  <button tooltip-text=\" $(gettext 'Log out  to console') \" use-underline=\"true\" width-request=\"120\" theme-icon-size=\"24\">
  <label>$(gettext 'Log out')</label>
  <input file icon=\"system-log-out\"></input>
  <action>openbox --exit &</action>
  </button>
  <button width-request=\"120\" theme-icon-size=\"24\">
  <label>$(gettext 'Cancel')</label>
  <input file icon=\"process-stop\"></input>
  <action type=\"exit\">Exit</action>
  </button>
  </hbox>   
  </vbox>
</window>
"

gtkdialog3 --program=shutdown --center

unset shutdown

/usr/share/applications/Logout

[Desktop Entry]
Type=Application
Name=Logout
Name[ru]=Выход
Comment= Shutdown, Suspend, Reboot, Restart WM,  or Logout
Comment[ru]=Выключить, Сон, Перезагрузить,  Перезапустить ВМ, или Выйти
Icon=system-shutdown
Exec=kla-shutdown

logout-banner.gif in /usr/share/pixmaps/kla-session/logout-banner.gif

Banner called KLA on fire

@Sofiya I guess it will take some hacking to make all options work.
As I experimented here: viewtopic.php?p=90301#p90301 Exit X (not restart X) can work but breaks RestartX. So it seems to me (from what I tested) that it's one or the other, not both.
Also what does "Logout" mean ? True logout IMO should be that you need to re- login with password again. Just exiting X will keep you logged in.
Having installed a login-manager such as e.g. slim can make that re- login work (but needs disabled the autologin at the getty systemd service).

Nice KLA on fire display btw

fredx181 wrote: ↑Wed May 31, 2023 5:14 pm

@Sofiya I guess it will take some hacking to make all options work.
As I experimented here: viewtopic.php?p=90301#p90301 Exit X (not restart X) can work but breaks RestartX. So it seems to me (from what I tested) that it's one or the other, not both.
Also what does "Logout" mean ? True logout IMO should be that you need to re- login with password again. Just exiting X will keep you logged in.
Having installed a login-manager such as e.g. slim can make that re- login work (but needs disabled the autologin at the getty systemd service).

Nice KLA on fire display btw

Also what does "Logout" mean ? True logout IMO should be that you need to re- login with password again. Just exiting X will keep you logged in.

yes if you turn off autologin it works as it should. I have no idea how @Wiak has it set up. This is somewhere in the build plugin you need to change the code. so let it be for now as it is

But without auto login, the user will be confused, as he will wait for the system to boot without implying that he must enter a login and password to continue logging in

Sofiya wrote: ↑Wed May 31, 2023 5:36 pm

But without auto login, the user will be confused, as he will wait for the system to boot without implying that he must enter a login and password to continue logging in

Yes, I'd say, keep the auto login.
I tried investigating : initial boot > autologin , ok, but then after boot : option to logout and login with password (on KLV we could make that work, but KLV has runit, not systemd).
Needs more knowledge about how to handle systemd services, don't know much about it, perhaps @wiak you have idea ?

fredx181 wrote: ↑Wed May 31, 2023 5:14 pm

@Sofiya I guess it will take some hacking to make all options work.
As I experimented here: viewtopic.php?p=90301#p90301 Exit X (not restart X) can work but breaks RestartX. So it seems to me (from what I tested) that it's one or the other, not both.
Also what does "Logout" mean ? True logout IMO should be that you need to re- login with password again. Just exiting X will keep you logged in.
Having installed a login-manager such as e.g. slim can make that re- login work (but needs disabled the autologin at the getty systemd service).

Nice KLA on fire display btw

After experimenting with your code, everything would be fine, but there is no exit from the console until you type exit to select the user further:ugeek:

@fredx181 I already have this all sorted out in Weedog64-Void from way back when which is KLV's predecessor and uses a JWM - ROX desktop.

There I have the ExitX option in the menu.

I will stop what I am doing in Colorado and try to track that down.....BUT all of this is on my machines in Connecticut.....looking at the map I don't think I can get to the archived data at the moment though due to my Beam me up Scotty isn't working yet

Sofiya wrote: ↑Wed May 31, 2023 6:11 pm

After experimenting with your code, everything would be fine, but there is no exit from the console until you type exit to select the user further:ugeek:

Typing startx brings me to the Desktop again, not for you ?
(btw, I only replaced the content of .bash_profile with my code (and rebooted!) , other settings kept default (e.g. autologin enabled).
EDIT: Fine also to keep all things as they are, of course, a user can get at the console on tty2 (by logging in first).

rockedge wrote:

due to my Beam me up Scotty isn't working yet

Yeah, Scotty isn't feeling well these days.

fredx181 wrote: ↑Wed May 31, 2023 6:33 pm

Sofiya wrote: ↑Wed May 31, 2023 6:11 pm

After experimenting with your code, everything would be fine, but there is no exit from the console until you type exit to select the user further:ugeek:

Typing startx brings me to the Desktop again, not for you ?

@fredx181
Yes, startx also brings me back to the desktop

fredx181 wrote: ↑Wed May 31, 2023 5:54 pm

perhaps @wiak you have idea ?

It was years ago that I made WDL_Arch64, which basically became KLA-OT2base, but I can't remember details except the Openbox menu I used was controlled from ~/.config/openbox/menu.xml, which called up my shell script /usr/local/bin/wd_exit. I haven't been following threads of late so I'm only guessing what you are talking about. I do remember something about having option to stop autologin and somewhere along the road I needed to enter an additional 'exit' to get login prompt at commandline, but I forget what that was all about and didn't need the option at the time.