Installing Conky

I downloaded the .deb-package conky-all yesterday and then compiled conky manager2 with the help of these instructions.
Do I still need to save the conky-manager2 programme in a specific location?
It is stated that you can delete the package with "sudo make uninstall". Does the terminal then know where the package conky-manager2 is located?

You don't need to do it, but it's best to keep things organized. For programs installed manually it's typical to locate them in either the /opt, /usr/local, or if your prefer to keep it local to your user, ~/.local/share.

No, you need to navigate to the folder where you downloaded the source code, using cd and run that command from there.

1 Like

Where was conky-manager2 installed and where was the source code stored? Can you see this from the commands executed?
This is what I entered:

apt install build-essential git valac libgee-0.8-dev libgtk-3-dev libjson-glib-dev gettext libgettextpo-dev p7zip-full imagemagick
git clone https://github.com/zcot/conky-manager2.git
cd conky-manager2
make
sudo make install

It's probably installed in multiple locations, not just one. You can find them with:

find /usr /etc -type d -iname "*conky*" 2>/dev/null

Or even more broad:

find / -maxdepth 3 -type d -iname "*conky*" 2>/dev/null

Increase the maxdepth if you want to search even more directories, keeping in mind that that further you go, the more it'll take to complete.

When You downloaded it with the git clone Command, it could be in the Downloads Folder.

I have found the conky-manager2 files in the following locations:

  1. ~/conky-manager2
  2. usr/share/conky-manager2

Should I merge them all into a single folder and then save it in /usr/local, for example?
Which child folder on the screenshot contains the source code?

It was not necessary to build it from the source, as an Ubuntu based distro you should have followed instructions for ppa and install it using apt. It's lot easier to manage with apt in case of removal.

2 Likes

I read here in the forum that there were problems with the use of ppas for conky. Aravisian recommended in a thread to compile the conky-manager2 yourself. That's why I tried it this way. But yes, it is quite complicated. Since I'm not familiar with ppas at all and so often some warnings appear because of it (e.g. before downloading or during updates/upgrades), they are a bit scary to me. I had looked at the teejee ppas before, but a lot of them are no longer maintained. There is still a ppa from tomtom or from ubuntuhandbook1 for the conky manager - yes, and it all kind of overwhelmed me.

1 Like

I'd suggest going with the easy route first, and only go for the compilation option if you run into any issues. I'm not familiar with Conky, so I'm not sure what issues are to be expected, but this would make things much easier.

There have been some drops, I think Tony George (TeeJee) is one of them.
But I actually do use the TomTomTom ppa, because it is maintained and up to date:

If you compiled from source, you are fine. There is no need to try shuffling file packages around, though. They install where they install for reason. Changing that is probably scarier than using a ppa....

It's already done. Uninstalling it now and installing the ppa instead makes no sense. Next time then! I didn't realise it was so much more difficult to manage on the system.
Or would it be better to do this because of getting updates for it? Will it stop working if I don't do this?

How safe is it to use additional software such as GNU Stow or Checkinstall for the self-compiled packages? Some can also handle Appimages.

It's only unsafe to use those programs if you don't understand how they work and use them incorrectly. For example, Stow has nothing to do with compiling software. I think it's best for you to stick with precompiled software from the PPA mentioned above, it'll save you a lot of headaches.