From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] php-5.6.33
Date: Fri, 27 Nov 2020 11:26:41 +0000 [thread overview]
Message-ID: <2443855.Lt9SDvczpP@lenovo.localdomain> (raw)
In-Reply-To: <03de3881-8b5d-76bb-d166-4dd253b3517e@sys-concept.com>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
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.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-27 11:27 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 [this message]
2020-11-27 15:03 ` thelma
2020-11-27 15:17 ` thelma
2020-11-27 15:42 ` Michael
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=2443855.Lt9SDvczpP@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