Re: [Gimp-user] Debian 11, updated, Gimp 2.10.22 - bad clone tool

[Dedeco Balaco <dedeco balaco yahoo com>]

Em 18/10/2021 19:13, Ken Moffat via gimp-user-list escreveu:
> On Sat, Oct 16, 2021 at 11:43:09PM -0300, Dedeco Balaco via gimp-user-list wrote:
> > I tried to compile 4 Gimp versions, and i tried to downgrade gimp
> > package too, downloading it from Debian repository. Nothing worked:
> >
> > gimp-2.10.0.tar.bz2   
> > gimp-2.6.12.tar.bz2        
> > gimp-2.8.22.tar.bz2
> > gimp-2.10.24.tar.bz2  
> > gimp_2.8.18-1+deb9u1_amd64.deb
> Hopefully, Liam has answered your questions re compiling the current
> 2.10 release and whatever has been changed in 2.10-git but not yet
> released.

I gave up compiling Gimp. It is too complex to compile. It demands
libraries of specific versions, and not only this. They also have to be
in specific intervals. Open source? Yes. But to compile it is a hard
work. So... not for normal people who just want to solve simple
problems, or change simple details which cannot be changed in settings.


> So I will merely add that trying to compile non-recent versions with
> recent versions of gcc, binutils, gtk2, and other dependencies is
> likely to fail - too much has changed.

Yes, it failed.


> I also don't see any point in trying to compile 2.10.0, nor any 2.8
> or 2.6 on a current system.  Leave that to people using old systems
> which do not have a recent gimp-2.10.

The point is simple: version 2.8 worked for me! And that is all i cared
about.


> > The sources complain about uninstalled packages, but i do not finding
> > which packages i should install. The name is not the one in the errors
> > given to me.
> >
> > For the package, *dpkg* complained a library i have is too new.
> >
> > Can you help me?
> >
> >
> > Em 16/10/2021 22:40, Dedeco Balaco via gimp-user-list escreveu:
> > > Soon, I will compile Gimp after doing *'configure'* with these arguments:
> > >
> > > $ ./configure --with-gimpdir=/dev/shm/.root/tmp/ \
> > > --with-shm=/dev/shm/.root/tmp/ \
> > > --disable-default-binary \
> > > --with-desktop-dir=/dev/shm/.root/bin/ \
> > > --prefix=/dev/shm/.root/
> > >
> > > Is there anything else i can do, for a test? I do not want to cause any
> > > minimal effect on the installed Gimp package in my Debian. I want to
> > > ignore it completely, from my preferences to everything else.
> Create a new user, for testing ?  Or, backup the system and be
> prepared to restore from the backup.

Yes. New user was possible. But i this would something i could fix with
some setting changed, no? And i did not find this setting.


> ISTR that debian has many variants, that 'sid' is usually close to
> current upstream releases, and that it is possible to mix sources
> (e.g. current, sid) although I do not recall how to do that.

(...)


> > > I am not an experienced developer with these things, so I will wait
> > > someone reply here, before *'make install'*ing it.
> > >
> > > Thank you    (:
> Passing the switches pointing to /dev/shm/.root/ looks very odd.
> I've no idea what --with/shm is for, but installing in /dev/shm may
> mean that only root can use it (unsure).  It is more conventional to
> use e.g. /opt/gimp (people also use /home/yourusername/gimp or
> similar but that might conflict with the debian install.

/dev/shm is a special place in linux. It is a folder which lives in
available RAM, and all users can read and write that, by default.
/dev/shm/.root is just a temporary extra root i use for compiling things
just for tests which, most of the time, i do not want or need to save or
cause effects in the real system, or in the real user settings.


> You need to export PATH and PKGCONFIG_PATH (put your chosen location
> at the front of each) for building the dependencies and gimp.
> Conventionally, if you end up building 6 packages to cover the
> required dependencies, put them all in the same prefix (it makes
> specifying PKGCONFIG_PATH easier - just the lib/pkgconfig {or
> lib64/pkgconfig if debian uses that} and share/pkgconfig for your
> prefix, follow both of those by the /usr variants.
>
> Most importantly, do a DESTDIR install on each package, e.g.  make
> DESTDIR=/tmp/PACKAGENAMR that will let you look at what will be
> installed, and if necessary blow away the compiled source and the
> DESTDIR before repeating with amended options.
>
> For anything using meson, export DESTDIR=/where/ever before running
> ninja install - and unset DESTDIR afterwards.

I gave up compiling gimp. Thank you, anyway, for these comments. It
shows that something else would be needed to change, besides what i
tried, which are the './configure' arguments.