| 1 |
Nope, not looking for --pretend. It is almost the opposite thing I need. Not what libpng is dependant on, but what is dependant on libpng. Let's say a new libpng is released and it doesn't need any new dependencies. I.e. an --pretend on libpng tells me that all it will install is the new libpng. This DOES NOT mean it is safe to emerge this new libpng as it could break all sorts of things that are compiled against the older libpng library. So what I'm wondering is if there is a way, or could be a way to catalog library dependencies, so I would know what needed to be re-emerged to compile against the updated libpng. |
| 2 |
|
| 3 |
Sean |
| 4 |
|
| 5 |
|
| 6 |
-----Original Message----- |
| 7 |
From: Bjarke Sørensen [mailto:bs@××××.dk] |
| 8 |
Sent: Thursday, May 02, 2002 11:52 |
| 9 |
To: Sean P. Kane |
| 10 |
Cc: gentoo-dev@g.o |
| 11 |
Subject: Re: [gentoo-dev] Emerge - check dependencies |
| 12 |
|
| 13 |
|
| 14 |
On Thu, May 02, 2002 at 11:03:55AM -0700, Sean P. Kane wrote: |
| 15 |
> Is there an easy way to check and see what packages could be effected |
| 16 |
> by upgrading a package like libpng? |
| 17 |
|
| 18 |
I hope you are not looking for |
| 19 |
# emerge --pretend <package> |
| 20 |
|
| 21 |
Else you can probably somthing like: |
| 22 |
# for x in `find /usr/portage/ -iname '*ebuild'`; do fgrep -i "libpng" ${x}; done |
| 23 |
|
| 24 |
Nah, that won't I give up.. don't think it's possible with current Portage (1) |
| 25 |
|
| 26 |
Sorry. |
| 27 |
-- |
| 28 |
| 9000.WASD |
| 29 |
| |
| 30 |
| Bjarke Sørensen |
| 31 |
| http://wasd.dk/ |
| 32 |
| |
| 33 |
| There are 10 types of people in this world: |
| 34 |
| Those who understand binary, and those who don't. |
Archives