First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 179663
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Crypto team <crypto@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Diego Pettenò <flameeyes@gentoo.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 179663 depends on: Show dependency tree
Show dependency graph
Bug 179663 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-05-24 16:58 0000
As per summary, libassuan installs only .a (archive, static) libraries, rather
than shared objects. This is usually against policy; even if the usage of
static library is reasoned, there are packages depending on libassuan at
runtime, but being only static, they should only depend on it at build time:

[18:54] <Flameeyes> !rrdep libassuan
[18:54] <jeeves> dev-libs/libassuan <- app-crypt/dirmngr app-crypt/gnupg
app-crypt/gnupg-pkcs11-scd

HTH,
Diego

------- Comment #1 From Alon Bar-Lev (RETIRED) 2007-05-24 17:04:22 0000 -------
There was a discussion of this in upstream.

Thread at:
http://lists.gnupg.org/pipermail/gnupg-devel/2006-December/023462.html

What do you recommend to do?

------- Comment #2 From Diego Pettenò 2007-05-25 10:23:37 0000 -------
Debian has a policy much similar to us, so I'd say follow whatever they are
doing; in this case, they are not using a shared library either, so until
libassuan devs release something that is stable and supported as shared object,
libassuan should be moved from RDEPEND to DEPEND.

------- Comment #3 From Alon Bar-Lev (RETIRED) 2007-06-13 08:09:10 0000 -------
Fixed.
Done waiting.
Thanks.

First Last Prev Next    No search results available      Search page      Enter new bug