| 1 |
Would there be any way to do this with the dependancy information already stored in the "/var/db/pkg" directory. It will probably be less accurate than the ldd sollution since it wouldn't necessarily mean that a binary or library was linked against a package, but it should at least give a "worst case senario" of what you might have to reemerge. |
| 2 |
|
| 3 |
--Michael |
| 4 |
|
| 5 |
On Wed, 26 Mar 2003 01:39:31 +0100 |
| 6 |
Per Wigren <wigren@××××.se> wrote: |
| 7 |
|
| 8 |
> Yesterday, for about 30 hours all my newly recieved mail went to /dev/null |
| 9 |
> because of a portage limitation... |
| 10 |
> I have an old computes which acts as a firewall/router, ftpserver webserver |
| 11 |
> and mailserver with IMAP and spamassassin... I have "mysql" in my USE-flags |
| 12 |
> on said server.. Yesterday portage upgraded MySQL from 3.23.56 to 4.0.12.. |
| 13 |
> postfix and maildrop both linked to /usr/lib/libmysqlclient.so.10 which went |
| 14 |
> away when MySQL was upgraded.. When the still running postfix delivered the |
| 15 |
> mail using dropmail, dropmail just died with "error while loading shared |
| 16 |
> libraries: no such file or directory" and for some reason (I'd call it a bug |
| 17 |
> in postfix) it didn't defer them, they just went to /dev/null... |
| 18 |
> Anyway, I won't whine about it.. Instead I'm looking into finding a solution |
| 19 |
> for the REAL problem... |
| 20 |
> |
| 21 |
> A solution I've been thinking about is this: |
| 22 |
> |
| 23 |
> When a package is installed portage will run ldd on all binaries and libs and |
| 24 |
> put its library-depends in a file in its /var/db/pkg-directory. |
| 25 |
> |
| 26 |
> Later when a package is upgraded, it will scan the LIBDEPS-files for broken |
| 27 |
> dependancies and tell the user something like: |
| 28 |
> * WARNING: The following packages needs to be reinstalled because of broken |
| 29 |
> dependancies: |
| 30 |
> * net-www/blabla |
| 31 |
> * app-games/blablabla |
| 32 |
> * media-video/blabla |
| 33 |
> |
| 34 |
> And when a package is uninstalled with -C or --clean, it will scan the |
| 35 |
> LIBDEPS-files for the libs it will remove and refuse to uninstall it if it |
| 36 |
> breaks anything. Maybe with a warning like this: |
| 37 |
> * WARNING: dev-libs/libblablabla can't be uninstalled because the following |
| 38 |
> packages depends on it: |
| 39 |
> * net-www/blabla |
| 40 |
> * app-games/blablabla |
| 41 |
> * media-video/blabla |
| 42 |
> * use --force to uninstall it anyway. |
| 43 |
> |
| 44 |
> |
| 45 |
> |
| 46 |
> Anyone have a better solution? |
| 47 |
> |
| 48 |
> Regards, |
| 49 |
> Per Wigren |
| 50 |
> |
| 51 |
> -- |
| 52 |
> gentoo-dev@g.o mailing list |
| 53 |
> |
| 54 |
> |
| 55 |
|
| 56 |
|
| 57 |
----------------------------------------------------------- |
| 58 |
Michael Taylor |
| 59 |
mtaylor@××××××××××.org |
| 60 |
|
| 61 |
-- |
| 62 |
gentoo-dev@g.o mailing list |
Archives