Got a working Gimp 1.2-Thanks Q
Hi, The Xemian gimp 1.2 seems to have done the trick. It does go in as ~/.gimp-1.2. Is this particular to the new gimp or this build? Any way to get an old generic .gimp (I moved my earlier one so as to avoid just this). Thanks. Jonathan
Re: Got a working Gimp 1.2-Thanks Q
[EMAIL PROTECTED] (2001-01-14 at 1945.45 +0100): The Xemian gimp 1.2 seems to have done the trick. It does go in as ~/.gimp-1.2. Is this particular to the new gimp or this build? Any way to get an old generic .gimp (I moved my earlier one so as to avoid just this). Gimp uses dirs with version so you can mix installs or it does not crash after a big update (some config items are not compatible). After getting "nice" cores with other apps, I think Gimp way is good, you can always move one item at a time, or edit by hand to match your old config (I did). GSR
Re: Got a working Gimp 1.2-Thanks Q
Guillermo S. Romero / Familia Romero wrote: Gimp uses dirs with version so you can mix installs or it does not crash after a big update (some config items are not compatible). After getting "nice" cores with other apps, I think Gimp way is good, you can always move one item at a time, or edit by hand to match your old config (I did). I can see the logic of it, but my only experience of gimp is 1.04 which did not do this. So the question was/is, is this a new feature of particular to this build? I tried changing the preferences directories to .gimp from .gimp-1.2 but it still created new directory. Any other way of getting a plain .gim back? Thanks. Jonathan
Re: Got a working Gimp 1.2-Thanks Q
On Sun, Jan 14, 2001 at 08:04:09PM +0100, "Guillermo S. Romero / Familia Romero" [EMAIL PROTECTED] wrote: Gimp uses dirs with version so you can mix installs or it does not This is not true,a nd far from easy in practise. Any binaries installed overwrite the older ones, so you need to use a different prefix use do rename orgies. Also, all components that are callable from outside (e..g perl) need to be speciall trated (modifications to your profile are needed as well as different configure options). (are we still using the ugly-but-maybe-necessary ~/.gimp-version convention?). Last not least, it is usually impossible to cleanly share different versions of gtk+ on the same host, as long as one of the prefixes that gtk+ uses coincide with prefixes where other programs (perl, libtiff etc..) are installed (e.g. /usr/gtk12 /usr/gtk13 is usually ok). This is a libtool limitation/an artifact of gtk-config. The same is true for gimp. So, people, don't try this at home unless you really know how to fix the resultant problems. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
