02-03-2021, 06:51 PM
(02-03-2021, 06:26 PM)rich2005 Wrote:Quote:1.) Is this the way things are normally supposed to be?That is correct. At the moment Gimp 2.10 accepts either the plugin executable or the executable in a folder of the same name. Certainly xsane is a symbolic link to wherever xsane is installed. rawphoto? is that some RAW loader.
Quote:2.) Can gimp "read" the contents of subdirectories that are not explicitly mentioned in the paths as specified in the preferences/foldersI suppose you can add a symbolic link (like the xsane one) to a file in one of the paths specified. Best way is add an extra path. The default for Gimp 2.8 (~/.gimp-2.8) was not too bad. When Gimp 2.10 came along so did my ~/gimp210/ folder structure. A bit more convenient than the regular one
Thanks, I saw your reply to the similar question in the windows section, after I posed this.
So then I guess that the name that gimp looks for to find the resynthesizer plug-in is "resynth-linux"? Regardless if it is gimp under debian, or gimp under ubuntu, or even gimp under Red Hat?
I think that is one of the things that keep us newbies so unsure of ourselves, never knowing where inviolable differences leave off, and compatibilities begin.
And the resynthesizer binaries and PY scripts all stay in that resynth-linux subdirectory?
I've decided to press myself and I'm going to try and encompass several of my desires into fixes, and then remaster my existing knoppix install into a new, live USB, making the patches permanent.
If some of these question seem anal, it's just because I'm trying avoid having to do it all twice.