| 1 |
yes it is, quickpkg is part of sys-apps/portage :-) |
| 2 |
|
| 3 |
$ equery b /usr/sbin/quickpkg |
| 4 |
* Searching for /usr/sbin/quickpkg ... |
| 5 |
sys-apps/portage-2.1.8.3 (/usr/lib64/portage/bin/quickpkg) |
| 6 |
sys-apps/portage-2.1.8.3 (/usr/sbin/quickpkg -> |
| 7 |
../lib64/portage/bin/quickpkg) |
| 8 |
|
| 9 |
On Sat, May 22, 2010 at 6:37 AM, Dale <rdalek1967@×××××.com> wrote: |
| 10 |
|
| 11 |
> Volker Armin Hemmann wrote: |
| 12 |
> |
| 13 |
>> On Samstag 22 Mai 2010, Dale wrote: |
| 14 |
>> |
| 15 |
>> |
| 16 |
>>> Hi, |
| 17 |
>>> |
| 18 |
>>> I think there is a way to do this but it's not sticking out at me on the |
| 19 |
>>> emerge man page. I'm doing a install and want to build a binary package |
| 20 |
>>> from my running system and install it on the new install. Basically, I |
| 21 |
>>> don't want to recompile, I just want emerge to copy the correct files |
| 22 |
>>> and make a tarball for me. |
| 23 |
>>> |
| 24 |
>>> I found the buildpkg option but that seems to compile it first then make |
| 25 |
>>> a tarball. Can I get it to skip the compile part? Is that a option |
| 26 |
>>> that portage has? |
| 27 |
>>> |
| 28 |
>>> Thanks. |
| 29 |
>>> |
| 30 |
>>> Dale |
| 31 |
>>> |
| 32 |
>>> :-) :-) |
| 33 |
>>> |
| 34 |
>>> |
| 35 |
>> quickpkg. |
| 36 |
>> |
| 37 |
>> Which has been mentioned hundreds of times on this list alone. |
| 38 |
>> |
| 39 |
>> |
| 40 |
>> |
| 41 |
> |
| 42 |
> That's not portage but it will work just fine and is what I am looking for. |
| 43 |
> I just need to read the right man page next time. ;-) |
| 44 |
> |
| 45 |
> Thanks much. |
| 46 |
> |
| 47 |
> Dale |
| 48 |
> |
| 49 |
> :-) :-) |
| 50 |
> |
| 51 |
> |
Archives