1 |
Turns out emerge has this nice flag (excerpt from emerge(1) manpage): |
2 |
|
3 |
--buildpkgonly, -B |
4 |
Creates binary packages for all ebuilds processed without |
5 |
actually merging the packages. This comes with the caveat that all |
6 |
build-time dependencies must already be emerged on the system. |
7 |
|
8 |
Best, |
9 |
mlen |
10 |
|
11 |
On Thu, Aug 9, 2018 at 9:29 AM Andreas Fink <finkandreas@×××.de> wrote: |
12 |
|
13 |
> On Wed, 8 Aug 2018 19:12:37 +0200 |
14 |
> tuxic@××××××.de wrote: |
15 |
> |
16 |
> > Hi, |
17 |
> > |
18 |
> > is it possible to go through process of installing a not-installed |
19 |
> > package from source to executable ... without actually install the |
20 |
> > package - so the system as such is not touched? |
21 |
> > |
22 |
> > Cheers |
23 |
> > Meino |
24 |
> > |
25 |
> > |
26 |
> > |
27 |
> |
28 |
> You can use ebuild for that. The commands to build without merging |
29 |
> would be |
30 |
> ebuild /usr/portage/my-package/my-ebuild-file.ebuild install |
31 |
> |
32 |
> This will download, unpack, build, and install the package into your |
33 |
> temporary portage build directory (usually /var/tmp/portage). It will |
34 |
> not resolve any dependencies though, this has to be done beforehand. |
35 |
> |
36 |
> The temporary install directory is called "image" in the temporary |
37 |
> directory. |
38 |
> |
39 |
> You can also go through the whole process step by step, |
40 |
> ebuild /usr/portage/my-package/my-ebuild-file.ebuild unpack |
41 |
> ebuild /usr/portage/my-package/my-ebuild-file.ebuild compile |
42 |
> ebuild /usr/portage/my-package/my-ebuild-file.ebuild install |
43 |
> ebuild /usr/portage/my-package/my-ebuild-file.ebuild qmerge |
44 |
> ebuild /usr/portage/my-package/my-ebuild-file.ebuild clean |
45 |
> |
46 |
> the qmerge command will install it into your system, so this is the |
47 |
> step, that you do not want to execute ;) |
48 |
> |
49 |
> Cheers |
50 |
> Andreas |
51 |
> |
52 |
> |