| 1 |
On Sun, Apr 27, 2008 at 8:33 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
|
| 3 |
> On Sat, Apr 26, 2008 at 1:00 PM, Alan McKinnon <alan.mckinnon@×××××.com> |
| 4 |
> wrote: |
| 5 |
> > On Saturday 26 April 2008, Mark Knecht wrote: |
| 6 |
> |
| 7 |
(...) |
| 8 |
|
| 9 |
> |
| 10 |
> > default so it's really slow). I'm thinking of these things: |
| 11 |
> > |
| 12 |
> > - Install every currently installed ebuild to an overlay, or install |
| 13 |
> > specific ebuilds or specific categories to an overlay. |
| 14 |
> > - Copy an installed ebuild and it's entire installed DEPEND tree to an |
| 15 |
> > overlay - this is for cases where <arb_lib> is not in world but is |
| 16 |
> > required as a deep dependency of something that is. The user will |
| 17 |
> > probably not be aware of this dependency and not having that ebuild |
| 18 |
> > will break stuff. |
| 19 |
> |
| 20 |
|
| 21 |
It hasn't been mentioned yet, but ebuilds of all installed packages can be |
| 22 |
found in /var/db/pkg/<category>/<pkg>-<ver>/<pkg>-<ver>.ebuild. emerge |
| 23 |
--sync can mess around with /usr/portage all it wants, your ebuilds will |
| 24 |
still be there until you unmerge the package. Right? |
| 25 |
|
| 26 |
|
| 27 |
> > - Copy an entire profile to an overlay |
| 28 |
> |
| 29 |
|
| 30 |
Could one integrate that with eselect profile? How about copying the current |
| 31 |
profile to /var/db/profile? |
| 32 |
|
| 33 |
|
| 34 |
> |
| 35 |
> > - Copy everything in an installed ebuild's SRC_URI (or all installed |
| 36 |
> > ebuilds) to a different DISTDIR for safety (think ATI driver downloads |
| 37 |
> > or kernels here) |
| 38 |
> |
| 39 |
> |
| 40 |
> > - Remove old ebuilds and profiles from the overlay that you have since |
| 41 |
> > upgraded |
| 42 |
> > - Possibly more |
| 43 |
> > |
| 44 |
> |
| 45 |
(...) |
| 46 |
|
| 47 |
> |
| 48 |
> Here's my idea: How hard would it be to have eix-test-obsolete |
| 49 |
> verify against the global database instead of the local database? If I |
| 50 |
> ran it that way *before* I ran emerge --sync then it would tell me |
| 51 |
> effectively which packages would be removed after syncing. I could |
| 52 |
> then move what I need to move by hand, run emerge --sync, and I'd |
| 53 |
> still be clean because I've saved my files into my private overlay |
| 54 |
> before the sync operation can delete them. |
| 55 |
|
| 56 |
|
| 57 |
This is about losing ebuilds? See comment about /var/db/pkg/... |
| 58 |
|
| 59 |
|
| 60 |
> |
| 61 |
> |
| 62 |
> If an enhancement like that is fairly simple - I have no idea - |
| 63 |
> then that would be a great start. Still, it's not protection against |
| 64 |
> the root cause of the problem, but it's a simple way to see ahead of |
| 65 |
> time what might happen. |
| 66 |
> |
| 67 |
> Cheers, |
| 68 |
> Mark |
| 69 |
> |
| 70 |
|
| 71 |
~Henry |
Archives