From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] php-5.6.33
Date: Fri, 27 Nov 2020 15:42:18 +0000 [thread overview]
Message-ID: <1854774.yKVeVyVuyW@lenovo.localdomain> (raw)
In-Reply-To: <93be3897-1f86-ccff-c469-5b1c6733caf3@sys-concept.com>
[-- Attachment #1: Type: text/plain, Size: 3036 bytes --]
On Friday, 27 November 2020 15:17:51 GMT thelma@sys-concept.com wrote:
> On 11/27/2020 04:26 AM, Michael wrote:
> > On Friday, 27 November 2020 07:24:57 GMT thelma@sys-concept.com wrote:
> >> I need to install old: php-5.6.33 on my new system. One program I have
> >> depends on it. Is it possible and what is the easiest way to go about
> >> it?
> >>
> >> I have the "php-5.6.33.ebuild" (and all other files) on my old system in
> >> dir:
> >> /var/db/pkg/dev-lang/php-5.6.33
> >>
> >> Is it possible to copy it to my: /usr/local/portage/dev-lang/
> >> and build it on my new system?
> >
> > There's two ways to go about it. Since the MoBo is the same, I would run
> > quickpkg then copy it over and emerge it on the new disk.
> >
> > Alternatively, copy over the ebuild and any associated files, then copy
> > over the source from distfiles and emerge it as you would normally emerge
> > a package.
> >
> > However, dependencies ...
> >
> > There are build time and run time dependencies. The emerge will fail if
> > build time dependencies are no longer available on the current portage
> > tree and/or fail to run if run time dependencies are missing. In this
> > case you'll have to fish these ebuilds out of the attic and try again.
> > Some packages will create conflicts with the currently installed
> > versions, which may become impossible to resolve. Which is why I
> > originally suggested cloning an already working system with all its
> > packages, rather than reinstalling.
> >
> > Either way, give quickpkg a spin and see where that gets you.
>
> I'll try as you suggested, the mother board is different, it is a new
> computer similar CPU AMD-8core.
Sorry, my misunderstanding. I thought it was the same hardware, but a
duplicate drive for dual booting.
> I've tried duplicating it with Gparted,
> didn't work.
> The disk are different as well.
> Old one is old WD spinning disk (about 10-years old)
> New one is M.2 SSD
Right, you could clone the disk, but then you would need to adjust your kernel
for the hardware it will be running on. If you have missing drivers it won't
work.
> Old system is: emerge --info
> Portage 2.3.24 (python 3.5.4-final-0, default/linux/amd64/17.0/desktop,
> gcc-6.4.0, glibc-2.25-r10, 4.9.72-gentoo x86_64)
>
> New one: emerge --info
> Portage 3.0.9 (python 3.7.9-final-0, default/linux/amd64/17.1/desktop,
> gcc-9.3.0, glibc-2.32-r2, 5.4.72-gentoo-x86_64 x86_64)
>
> So I'm not sure if duplicating the drive would work, maybe I'm going the
> wrong way about it. It would be nice if gentoo have an easier way of
> doing it, it would stand out from other distros. I've tried Debian
> (stable) it didn't work, and I know I have more flexibility with Gentoo.
>
> Thelma
I expect quickpkg will work, but it depends on the application's runtime
dependencies. Use quickpkg for those too if the package asks for any and see
what you get.
Ideally you should be looking at updating the application, or finding an
alternative which is still being maintained.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-11-27 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 7:24 [gentoo-user] php-5.6.33 thelma
2020-11-27 11:26 ` Michael
2020-11-27 15:03 ` thelma
2020-11-27 15:17 ` thelma
2020-11-27 15:42 ` Michael [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1854774.yKVeVyVuyW@lenovo.localdomain \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox