Install & Keep Multiple Versions

Xelvet · 2018-08-25 18:49:25

How can i install gimp 2.10
along-side with 2.8?

Coz 2.10 breaks all
my plugin-scripts.

Trilby · 2018-08-26 16:03:37

Your best bet would be to figure out why your plugin-scripts break and fix the problem.

The only way to install an older version would be to modify the PKGBUILD to build the old version and install to /usr/local/. But given GIMPs dependency chain this might prove to be highly impractical.

Xelvet · 2019-01-27 02:58:53

Fat chance.

Trilby wrote:

Your best bet would be to figure out why your plugin-scripts break and fix the problem.

Without recompiling?
gimp-2.10.8-1-x86_64.pkg.tar.xz
how to install that to /usr/local or /opt?
then i can just downgrade to 2.8.

the deps seem to be ok. coz i can
run both w/o downgradin any other pkgs.

Trilby wrote:

YThe only way to install an older version would be to modify the PKGBUILD to build the old version and install to /usr/local/. But given GIMPs dependency chain this might prove to be highly impractical.

usage:  pacman {-Q --query} [options] [package(s)]
-r, --root <path>    set an alternate installation root
Specify an alternative installation root (default is /). 
This should not be used as a way to install software into
/usr/local instead of /usr.

Or where can i get the PKGBUILD for 2.8?
I need both vers at the same time.
What exactly should be done?

Last edited by Xelvet (2019-01-27 03:05:50)

loqs · 2019-01-27 17:40:28

Xelvet wrote:

Fat chance.
Trilby wrote:
Your best bet would be to figure out why your plugin-scripts break and fix the problem.

Why?

Xelvet wrote:

Trilby wrote:
YThe only way to install an older version would be to modify the PKGBUILD to build the old version and install to /usr/local/. But given GIMPs dependency chain this might prove to be highly impractical.
usage:  pacman {-Q --query} [options] [package(s)]
-r, --root <path>    set an alternate installation root
Specify an alternative installation root (default is /). 
This should not be used as a way to install software into
/usr/local instead of /usr.

Yes you could install a new system using --root with the packages from a date when gimp version 2.8 was in the repositories.

Xelvet wrote:

Or where can i get the PKGBUILD for 2.8?
I need both vers at the same time.
What exactly should be done?

https://git.archlinux.org/svntogit/pack … db65169bcf
investigate the --prefix and -sysconfdir options and changing them so the contents does not clash.

Slithery · 2019-01-27 18:23:24

Use 2.10 from the repos and then install the 2.8 flatpak alongside?

eschwartz · 2019-01-27 18:49:35

And it took you 5 months to get get back to us after Trilby's initial response?

Xelvet wrote:

Fat chance.
Trilby wrote:
Your best bet would be to figure out why your plugin-scripts break and fix the problem.

So you're unwilling to find out why your scripts broke, but you'd rather try to figure out how to compile the entire gimp package yourself?

Without recompiling?
gimp-2.10.8-1-x86_64.pkg.tar.xz
how to install that to /usr/local or /opt?
then i can just downgrade to 2.8.

Quite obviously with recompiling. You want to build an old version of gimp using new system software, but you don't want to recompile?

Xelvet · 2019-01-27 23:53:37

loqs wrote:

Why?

eschwartz wrote:

So you're unwilling to find out why your scripts broke,
but you'd rather try to figure out how to compile the entire gimp package yourself?

Not my scripts & even registry.gimp.org scripts-repo is dead.
Gimp 2.9/2.10 has broken a bunch of scripts not just one or two.

eschwartz wrote:

And it took you 5 months to get get back to us after Trilby's initial response?

Yep, i had been stuck with 2.8 but now i realize the latest branch has some prety appealing new features.

logs wrote:

https://git.archlinux.org/svntogit/pack … db65169bcf
investigate the --prefix and -sysconfdir options and changing them so the contents does not clash.

Investigating. Where did you get that build-file?

logs wrote:

Yes you could install a new system using --root with the packages from a date when gimp version 2.8 was in the repositories.

As with systemd-nspawn containerization?

Slithery wrote:

Use 2.10 from the repos and then install the 2.8 flatpak alongside?

Flatpak hmmm -- interesting but I don't see any flatpaked 2.8 out there --
only the latest version & it isn't that much slim it seems with all the deps.

eschwartz wrote:

Quite obviously with recompiling. You want to build an old version of gimp using new system software, but you don't want to recompile?

Well usually yes-- with; but in this case as long as no deps have been backwardly-
or-forwardly broken yet, it seems. Why not. As a temp solution perhaps.

Can prefix be
changed in a package
which has already been built?
That's just install-path-location isn't it?

Last edited by Xelvet (2019-01-27 23:58:21)

loqs · 2019-01-28 00:46:37

Xelvet wrote:

loqs wrote:
Why?
eschwartz wrote:
So you're unwilling to find out why your scripts broke,
but you'd rather try to figure out how to compile the entire gimp package yourself?
Not my scripts & even registry.gimp.org scripts-repo is dead.
Gimp 2.9/2.10 has broken a bunch of scripts not just one or two.

If you could post one of the scripts or a link to it and the issue with it it perhaps it could be made to work with 2.10.

Xelvet wrote:

logs wrote:
https://git.archlinux.org/svntogit/pack … db65169bcf
investigate the --prefix and -sysconfdir options and changing them so the contents does not clash.
Investigating. Where did you get that build-file?

From web interface to the arch svn2git for packages which contains all package build changes for core and extra.
I started off at https://www.archlinux.org/packages/extra/x86_64/gimp/ from there view changes and checked commit messages looking for the last entry for 2.8.

Xelvet wrote:

logs wrote:
Yes you could install a new system using --root with the packages from a date when gimp version 2.8 was in the repositories.
As with systemd-nspawn containerization

Yes as trying to just install one package in a different root will not work as pacman will look for its database files relative to the root same issue with package dependencies etc.

There are two issues with trying to adjust the gimp 2.8 package arch shipped one is the file locations being the same as gimp 2.10 the other is the dependencies are for libraries as arch shipped months ago not now.

Xelvet · 2019-01-28 04:32:02

loqs wrote:

From web interface to the arch svn2git for packages which contains all package build changes for core and extra.
I started off at https://www.archlinux.org/packages/extra/x86_64/gimp/ from there view changes and checked commit messages looking for the last entry for 2.8.

I have compiled your PKGBUILD
but as soon as i try to install it with

pacman -U gimp-2.8.22-1-x86_64.pkg.tar.xz
warning: downgrading package gimp (2.10.8-1 => 2.8.22-1)

I changed the prefix to /usr/local
but how can i install it now alongside with 2.10
& keep em both without downgrading?
Renaming it w/o rebuilding?

Last edited by Xelvet (2019-01-28 04:57:28)

Lone_Wolf · 2019-01-28 11:13:38

You'll have to change the pkgname of your custom gimp version, something like gimp28 .

Check man makepkg , there are options to avoid complete rebuilds in special cases.

Xelvet · 2019-01-28 13:02:00

Lone_Wolf wrote:

You'll have to change the pkgname of your custom gimp version, something like gimp28 .
Check man makepkg , there are options to avoid complete rebuilds in special cases.

yeah -R can rename; but not if
one needs to change the prefix too.

man, why /usr/local
is preceding /usr
in $PATH env..

loqs · 2019-01-28 15:50:21

From configure --help

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
  --program-suffix=SUFFIX            append SUFFIX to installed program names
  --program-transform-name=PROGRAM   run sed PROGRAM on installed program names

So

_pkgver=2.8
./ configure --program-suffix=-${_pkgver} \

All the binaries will then use the -2.8 suffix distinguishing them from the binaries supplied by the gimp package.

Xelvet · 2019-01-28 21:35:13

Either way it isn't
going to install itself
with the /usr/local prefix..

% x p -U gimpp-2.8.22-1-x86_64.pkg.tar.xz
error: failed to commit transaction (conflicting files)
gimpp: /usr/local/share/man exists in filesystem (owned by filesystem)

% ls /usr/local/share/
lrwxrwxrwx 1 root root    6 Aug 21 16:21 man -> ../man

loqs · 2019-01-28 21:54:42

./configure --mandir=/opt/local/man

Xelvet · 2019-01-28 23:14:15

Oh man,
yeah i installed
it finally under /opt.
But why, the dir is
a symlink & empty..

loqs · 2019-01-28 23:40:24

pacman does not follow symlinks that link predates that pacman change. It was initially added in https://git.archlinux.org/svntogit/pack … 124385a079
See http://refspecs.linuxfoundation.org/FHS … OCALSHARE1 requirement appears to have been dropped in FHS 3.0 http://refspecs.linuxfoundation.org/FHS … ocalshare1

Arch Linux

#1 2018-08-25 18:49:25

Install & Keep Multiple Versions

#2 2018-08-26 16:03:37

Re: Install & Keep Multiple Versions

#3 2019-01-27 02:58:53

Re: Install & Keep Multiple Versions

#4 2019-01-27 17:40:28

Re: Install & Keep Multiple Versions

#5 2019-01-27 18:23:24

Re: Install & Keep Multiple Versions

#6 2019-01-27 18:49:35

Re: Install & Keep Multiple Versions

#7 2019-01-27 23:53:37

Re: Install & Keep Multiple Versions

#8 2019-01-28 00:46:37

Re: Install & Keep Multiple Versions

#9 2019-01-28 04:32:02

Re: Install & Keep Multiple Versions

#10 2019-01-28 11:13:38

Re: Install & Keep Multiple Versions

#11 2019-01-28 13:02:00

Re: Install & Keep Multiple Versions

#12 2019-01-28 15:50:21

Re: Install & Keep Multiple Versions

#13 2019-01-28 21:35:13

Re: Install & Keep Multiple Versions

#14 2019-01-28 21:54:42

Re: Install & Keep Multiple Versions

#15 2019-01-28 23:14:15

Re: Install & Keep Multiple Versions

#16 2019-01-28 23:40:24

Re: Install & Keep Multiple Versions

Board footer