name mode size
.DirIcon 120000
.tx 040000
Config 040000
Help 040000
debian 040000
po 040000
po4a 040000
poxml 040000
src 040000
.gitignore 100644 1.1kB 100644 3.02kB
AUTHORS 100644 119B 100644 523B
AppRun 100755 2.6kB
COPYING 100644 18.09kB
COPYING-LGPL 100644 7.65kB
ChangeLog.old 100644 116.09kB
INSTALL 100644 1.05kB
INSTALL.Debian 100644 193B
NEWS 100644 33B 100644 8.56kB
README.translations 100644 536B
TODO 100644 103B
genlog 100755 1.25kB 100644 107.63kB 100755 29.84kB 100644 5.05kB 100644 12.62kB 100644 1.12kB
roxterm.desktop 100644 7.99kB 100644 790B 100644 1.86kB
roxterm.svg 100644 21.58kB
roxterm.xml 100644 411B
update-tags 100755 208B
upload 100755 297B 100755 114B
Roxterm ---- Not by Apollia. Most notes by Apollia from Jan. 7, 2018 or before. I (Apollia) slightly modified the "lucid" branch, just to get rid of an annoying "Error connecting to dbus" dialog box that popped up every time I launched Roxterm with Openbox, and also when I tried to open the "Edit Current Profile" and "Edit Current Colour Scheme" items in the Preferences menu after launching Roxterm with Openbox. ----- Note, Sept. 13, 2018. I didn't add this to my self-hosted Git repos back in June 2018 (when I deleted all my repos from GitHub) because something quite confusing happened with the branches. I still don't understand what the problem is. Originally, it looked like the lucid branch had somehow gone missing, but somehow: git checkout lucid ...still worked, even though this command: git branch -a ...showed only this output originally: * master remotes/origin/HEAD -> origin/master remotes/origin/lucid remotes/origin/master <br>After checking out the lucid branch, this was the output of git branch -a: git branch -a * lucid master remotes/origin/HEAD -> origin/master remotes/origin/lucid remotes/origin/master <br>Fortunately, I can still build Roxterm from source using the lucid branch, so I decided to upload this repo, even though I still don't know exactly what went wrong with the branches. I don't think I ever used branches in my own repos, so at least my own repos are hopefully probably intact. End of Sept. 13, 2018 note by Apollia. ---- Here's the page where I learned how to clone the Roxterm repo: * And here's the command I used, which I copied and pasted from that web page: git clone git:// roxterm On Jan. 6, 2018, I ran that command, then uploaded the repo to GitHub. <br><br> I changed the repo's remote URL with this command: git remote set-url origin Then, to upload the repo's tags, I used this command: git push origin --tags <br><br> I eventually saw on this page - - that there is also a "lucid" branch "For older distros which do not include packages of GTK3 etc". So, I retrieved that and uploaded it to this GitHub repo also. ---- I cloned this because I always liked Roxterm in Lucid Puppy Linux 5.2.8 version 004 - - but it's not included in Lighthouse 64 Puppy Linux 6.02 Beta 2. Also, the original developer is no longer working on Roxterm - But, it's still useful to me, so I wanted to at least make a backup copy. Don't know if I'll change anything in it in the future, but maybe. ---- ## Building Roxterm in Lighthouse 64 Puppy Linux 6.02 Beta 2 I had a difficult time with this, and I'm still not sure I did it right. ### My failed attempt to build the latest version of Roxterm The latest version required me to get: * Python 3. I compiled [Python 3.6.4](, which fortunately went quite smoothly. * ITS Tool. I compiled [ITS Tool version 2.0.4](, which also was easy. * GTK 3.10. Eventually figured out I needed [version 3.10.1]( so ./configure wouldn't fail when it couldn't find "wayland-scanner". But, there were so many other things GTK 3.10 required me to upgrade that I gave up. ### My possibly successful attempt to build the "lucid" branch of Roxterm - Version According to this page - - there is a "lucid" branch in this repo "For older distros which do not include packages of GTK3 etc". Which sounded like exactly what I needed, so, I decided to build it, even though I already had version 2.0.0 working. I haven't used either version very much yet, so I'm not sure which one is better. I'll update this with more details if/when I try compiling any other later versions. <br><br> Like the other builds, I figured this out via trial and error, clues from the web, and the repo's INSTALL file. <br><br> First, I did this: git checkout lucid Then: ./ configure --no-lock --disable-gtk3 --disable-git ./ build --no-lock <br><br> Then I renamed the Roxterm folder to "Roxterm-" to avoid confusing the new2dir script. Then, to make a Puppy Linux .pet file, I ran: new2dir ./ install --no-lock <br><br> However, for some reason, this resulted in a .pet which installed files to the wrong locations. (In fact, I think `./ install --no-lock` by itself installs the files to the wrong locations. But I couldn't figure out how to fix that.) So, I had to right-click on the .pet, choose "Extract-pet", open the pet folder "roxterm-", and put the /usr/ folder at the top level of the pet folder. Then I remade the .pet file with this command: dir2pet roxterm- Then, to install the files to the correct locations, you can run that remade .pet file. ### My possibly mostly successful attempt to build Roxterm 2.0.0 This was my first (possibly, mostly) successful build of Roxterm. I couldn't recall what version of Roxterm was in [Lucid Puppy Linux 5.2.8 version 004](, so, I decided to try compiling Roxterm 2.0.0, the most recent version of Roxterm released prior to Lucid Puppy 5.2.8-004's release date - August 17, 2011. Later, I figured out how to compile the "lucid" branch's version (Instructions above.) I haven't used either version very much yet, so I'm not sure which one is better. * In my Roxterm repo folder, I ran this command line: git checkout 2.0.0 <br> * I tried to run ./, but it complained about the lack of So, I tracked that down, and downloaded its source package in .tar.xz format from this page: <br><br> <br><br> I unzipped that, and soon found the files I needed were in the "scripts" folder. I manually put and the Dpkg folder inside my computer's /usr/local/lib64/perl5 folder. If I recall correctly, that made it so I could run successfully. <br> * However, ./configure didn't work right yet - there was some sort of error about "config.sub". But, I found a solution at this page: <br><br> <br><br> All I had to do was run: autoreconf --install ...inside the Roxterm folder. Then, ./configure worked. <br> * The "make" command seemed to work fine until the end, when I got these errors: ``` make[3]: Leaving directory `/root/00-ApWorkspace/roxterm/src' make[2]: Leaving directory `/root/00-ApWorkspace/roxterm/src' Making all in po4a make[2]: Entering directory `/root/00-ApWorkspace/roxterm/po4a' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/00-ApWorkspace/roxterm/po4a' make[2]: Entering directory `/root/00-ApWorkspace/roxterm' xmlto man roxterm.1.xml Note: Writing roxterm.1 make[2]: *** [roxterm.1] Error 1 make[2]: Leaving directory `/root/00-ApWorkspace/roxterm' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/00-ApWorkspace/roxterm' make: *** [all] Error 2 ``` <br> But, to my surprise, in the "src" folder of my Roxterm Git repo folder, there was a runnable "roxterm" file. But, you shouldn't run it yet, because I think doing that is what somehow caused my Roxterm to lack keyboard shortcuts. I also got errors (and no edit windows appeared) when I tried to use the "Edit Current Profile" and "Edit Current Colour Scheme" items from the Preferences menu. <br><br> (Fortunately, after correctly installing Roxterm, those menu items started working. And I was able to fix the missing keyboard shortcuts problem by deleting the "" folder from my /root/.config folder.) <br><br> To avoid those errors, I think it's best to install Roxterm before running it, such as by running the command "new2dir make install" in the Roxterm Git repo folder. <br><br> (Probably just "make install" would work too, but I wanted to create a Puppy Linux .pet file using new2dir.) <br><br> End of text by Apollia. ---- ROXterm - VTE/GTK terminal emulator with tabs See index.html in the Help subdirectory for full information.