| 1 |
On 6/13/06, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> |
| 3 |
> On Tue, 13 Jun 2006 09:40:47 -0700, Kevin O'Gorman wrote: |
| 4 |
> |
| 5 |
> > I may have a need to install one or more binary packages to fix |
| 6 |
> > a problem I'm having. These are ones that have been made for |
| 7 |
> > my system during normal emerges, but have since been pruned from |
| 8 |
> > the system. |
| 9 |
> > |
| 10 |
> > My question: how to clean up when I'm done? A cursory look at |
| 11 |
> > the packages makes me think they're plain tar archives with no |
| 12 |
> > metadata. How do I get rid of them when I'm done with them? |
| 13 |
> |
| 14 |
> There is metadata appended to the end of the file. If you try unpacking |
| 15 |
> one, you'll see a warning about extraneous data, this is the metadata. |
| 16 |
> |
| 17 |
> > Or must I install them using some tool that creates the metadata? |
| 18 |
> |
| 19 |
> What's wrong with installing with portage? Provided the packages are in |
| 20 |
> $PKGDIR, you can install with "emerge --usepkgonly packagename". You can |
| 21 |
> then unmerge in the usual way. |
| 22 |
> |
| 23 |
> If the package is one that prevents you from using portage, unpack it to |
| 24 |
> the root of your filesystem, then immediately use the above command to |
| 25 |
> emerge it properly. |
| 26 |
> |
| 27 |
> |
| 28 |
> -- |
| 29 |
> Neil Bothwick |
| 30 |
> |
| 31 |
> Failure is not an option...it is integrated with every Microsoft product. |
| 32 |
> |
| 33 |
> |
| 34 |
> Something about this is just not clicking with me. I restored my backup |
| 35 |
to |
| 36 |
an empty directory, chrooted to that directory, ran quickpkg on some of the |
| 37 |
packages I've been trying to re-emerge, and was feeling good. But... |
| 38 |
|
| 39 |
I got out of chroot, copied these to $PKGDIR (/usr/portage/packages) like |
| 40 |
the other packages there, and tried to emerge. No joy. Examples of |
| 41 |
what I tried: |
| 42 |
|
| 43 |
> treat Backups # emerge -v --usepkgonly =glib-1.2.10-r5 |
| 44 |
> Calculating dependencies |
| 45 |
> !!! There are no packages available to satisfy: "=glib-1.2.10-r5" |
| 46 |
> !!! Either add a suitable binary package or compile from an ebuild. |
| 47 |
> |
| 48 |
> treat Backups # |
| 49 |
|
| 50 |
|
| 51 |
and |
| 52 |
|
| 53 |
> treat dev-libs # emerge -v --usepkgonly ./glib-1.2.10-r5.tbz2 |
| 54 |
> emerging by path implies --oneshot... adding --oneshot to options. |
| 55 |
> |
| 56 |
> *** emerging by path is broken and may not always work!!! |
| 57 |
> |
| 58 |
> Calculating dependencies |
| 59 |
> *** You need to adjust PKGDIR to emerge this package. |
| 60 |
> |
| 61 |
> treat dev-libs # |
| 62 |
> |
| 63 |
|
| 64 |
|
| 65 |
But this one, for instance, was |
| 66 |
/usr/portage/packages/dev-libs/glib-1.2.10-r5.tbz2 |
| 67 |
and PKGDIR is |
| 68 |
/usr/portage/packages |
| 69 |
so what am I doing wrong now? |
| 70 |
|
| 71 |
This is getting demoralizing. |
| 72 |
|
| 73 |
++ kevin |
| 74 |
-- |
| 75 |
Kevin O'Gorman, PhD |
Archives