WetGeek it's not in the Solus repos. The package build spec and package.yml file are on my personal github.

If you're interested in trying it, you can contact me off site and I can get you the completed eopkg. You'll have to set up your own local repository to install it. It's like a version of Gnome terminal went on a diet.

Side note for anyone, is there a reason I shouldn't host my own personally created eopkg packages on github? It was mentioned on the dev site, but I honestly didn't inquire too much as why it shouldn't be there.

      WetGeek probably should have added that this is more of a learning/passion project for me. Compiling and packaging software I like or find useful, that can't be found as a snap or Flatpak, as an eopkg. It helps me learn Linux, learn git, learn the CLI, and learn more about Solus as I go.

      Nothing hosted on my github is endorsed, sponsored, or otherwise affiliated with Solus or the team. Some like @algent have been extremely helpful with comments, helping me understand when I've include redundant build deps and troubleshoot problems. And honestly, I wouldn't have even been able to do it without Josh's youtube video.

          Brucehankins Nice work! Sounds like I have a similar background as you (not a coder/programmer and no idea what I'd be doing), and also interested in learning Solus packaging. Seems like a challenging yet rewarding journey. Thanks for sharing some of your learning experiences here!

              h3o Thanks for the kind words! I'm always up for a challenge, so if there's something you'd like to packaged that isn't available via repos, snap, or Flatpak like Sakura, Featherpad, or KBackup, let me know and I'll give it a shot. Contact info is on my github and in my forum bio.

                  Brucehankins it's not in the Solus repos

                  Sorry ... I misunderstood your post. No worries at all, I was just curious about trying a new terminal emulator. I'm actually very satisfied with bash.

                      WetGeek I added the .eopkg file to my github and some disclaimers go along with using unofficial software.

                      It's a new project for me, so feel free to check it out and make any comments you wish. I always like feedback on how I can improve.

                          Brucehankins leaps and bounds for you----very cool.

                          edit: so what do I do after I download the .eopkg? Manually move it to all the other .eopkgs? Or change directory and install it via (ironically) with my gnome-terminal (sudo eopkg it etc)? I did the readme!🙂

                              brent Instructions Here on setting up a local repo and installing. And more information here on setting priority, etc. A note on priority: "eopkg will always prefer packages from the topmost repository listed with eopkg lr" I left the shannon repos as my topmost, to prefer that over my local. How you set it up is up to you and what you think best practice is.

                              Once you've set up the local repo/directory and indexed it, you can either install through gnome terminal with sudo eopkg it sakura or it will show up when you search for it in the Software Center.

                                  Brucehankins thank you. I'm stuck at giving my local repo an equally Irish boy name (opposite Shannon). Seamus, maybe. Or Ikey😉
                                  If I run into permission problems I will get back to you. When I test drive it, I will also get back to you!

                                      WetGeek I was just curious about trying a new terminal emulator. I'm actually very satisfied with bash.

                                      bash is a shell i.e. the language you use to write commands in the terminal. terminal emulators are programs like gnome-terminal, kitty, alacritty, etc. that provide the interface to type in 🙂

                                          synth-ruiner terminal emulators are programs like gnome-terminal,

                                          Yeah, sometimes I conflate the container with its contents. Thanks for the reminder.

                                            So I've got a new question about packaging. How do I update a package I've built using solbuild? I read the Updating an Existing Package, but that doesn't help.
                                            For example, I've packaged Sakura 3.8.1, but I want to update it to 3.8.2, how would that be done? Packaging 3.8.2 is no problem, but I'd like to learn additional steps in the process.

                                              Brucehankins From the docs it is recommended to use this alias:
                                              alias updatePackage='/usr/share/ypkg/yupdate.py', personally I use it as updateYml.
                                              I also use this alias to generate a Makefile in the package build folder:
                                              alias makefile='echo "include ../Makefile.common" > Makefile'

                                              In this case the update should be like this:
                                              updatePackage 3.8.2 https://launchpad.net/sakura/trunk/3.8.2/+download/sakura-3.8.2.tar.gz
                                              The release number will be automatically updated to +1.

                                                5 days later

                                                Sakura 3.8.2 is up on my github and currently works with Budgie* DE and Shannon repos. There are some bugs, opacity doesn't seem to work properly. I think this is most likely an issue with the source code rather than the packaging, but I'm looking into it.

                                                *I only test it on Budgie because that's what I use and I'm too lazy to set up a VM for Gnome. Also don't want to install all the GTK dependencies on my Plasma environment.