1 |
On Friday, 27 November 2020 15:17:51 GMT thelma@×××××××××××.com wrote: |
2 |
> On 11/27/2020 04:26 AM, Michael wrote: |
3 |
> > On Friday, 27 November 2020 07:24:57 GMT thelma@×××××××××××.com wrote: |
4 |
> >> I need to install old: php-5.6.33 on my new system. One program I have |
5 |
> >> depends on it. Is it possible and what is the easiest way to go about |
6 |
> >> it? |
7 |
> >> |
8 |
> >> I have the "php-5.6.33.ebuild" (and all other files) on my old system in |
9 |
> >> dir: |
10 |
> >> /var/db/pkg/dev-lang/php-5.6.33 |
11 |
> >> |
12 |
> >> Is it possible to copy it to my: /usr/local/portage/dev-lang/ |
13 |
> >> and build it on my new system? |
14 |
> > |
15 |
> > There's two ways to go about it. Since the MoBo is the same, I would run |
16 |
> > quickpkg then copy it over and emerge it on the new disk. |
17 |
> > |
18 |
> > Alternatively, copy over the ebuild and any associated files, then copy |
19 |
> > over the source from distfiles and emerge it as you would normally emerge |
20 |
> > a package. |
21 |
> > |
22 |
> > However, dependencies ... |
23 |
> > |
24 |
> > There are build time and run time dependencies. The emerge will fail if |
25 |
> > build time dependencies are no longer available on the current portage |
26 |
> > tree and/or fail to run if run time dependencies are missing. In this |
27 |
> > case you'll have to fish these ebuilds out of the attic and try again. |
28 |
> > Some packages will create conflicts with the currently installed |
29 |
> > versions, which may become impossible to resolve. Which is why I |
30 |
> > originally suggested cloning an already working system with all its |
31 |
> > packages, rather than reinstalling. |
32 |
> > |
33 |
> > Either way, give quickpkg a spin and see where that gets you. |
34 |
> |
35 |
> I'll try as you suggested, the mother board is different, it is a new |
36 |
> computer similar CPU AMD-8core. |
37 |
|
38 |
Sorry, my misunderstanding. I thought it was the same hardware, but a |
39 |
duplicate drive for dual booting. |
40 |
|
41 |
|
42 |
> I've tried duplicating it with Gparted, |
43 |
> didn't work. |
44 |
> The disk are different as well. |
45 |
> Old one is old WD spinning disk (about 10-years old) |
46 |
> New one is M.2 SSD |
47 |
|
48 |
Right, you could clone the disk, but then you would need to adjust your kernel |
49 |
for the hardware it will be running on. If you have missing drivers it won't |
50 |
work. |
51 |
|
52 |
|
53 |
> Old system is: emerge --info |
54 |
> Portage 2.3.24 (python 3.5.4-final-0, default/linux/amd64/17.0/desktop, |
55 |
> gcc-6.4.0, glibc-2.25-r10, 4.9.72-gentoo x86_64) |
56 |
> |
57 |
> New one: emerge --info |
58 |
> Portage 3.0.9 (python 3.7.9-final-0, default/linux/amd64/17.1/desktop, |
59 |
> gcc-9.3.0, glibc-2.32-r2, 5.4.72-gentoo-x86_64 x86_64) |
60 |
> |
61 |
> So I'm not sure if duplicating the drive would work, maybe I'm going the |
62 |
> wrong way about it. It would be nice if gentoo have an easier way of |
63 |
> doing it, it would stand out from other distros. I've tried Debian |
64 |
> (stable) it didn't work, and I know I have more flexibility with Gentoo. |
65 |
> |
66 |
> Thelma |
67 |
|
68 |
I expect quickpkg will work, but it depends on the application's runtime |
69 |
dependencies. Use quickpkg for those too if the package asks for any and see |
70 |
what you get. |
71 |
|
72 |
Ideally you should be looking at updating the application, or finding an |
73 |
alternative which is still being maintained. |