Bug 783965

Summary:	Should provide aliases as crypto++
Product:	[Fedora] Fedora	Reporter:	Dag Odenhall <dag.odenhall>
Component:	cabal-install	Assignee:	Jens Petersen <petersen>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	alekcejk, haskell-devel, metherid, petersen
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-24 01:16:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dag Odenhall 2012-01-23 11:41:42 UTC

Description of problem:

Other systems call the cryptopp library crypto++, leading to incompatibilities in Fedora.

Steps to Reproduce:
1.sudo yum install cabal-install openssl-devel cryptopp-devel
2.cabal update
3.cabal install happstack-server-6.5.1
  
Actual results:

cabal: Missing dependency on a foreign library:
* Missing C library: crypto++

Expected results:

Registering happstack-server-6.5.1...

Additional info:

http://packages.ubuntu.com/oneiric/i386/libcrypto++-dev/filelist

Comment 1 nucleo 2012-01-23 12:17:33 UTC

This is bug in cabal.
Crypto++ upstream recommends to use cryptopp names i.e /usr/include/cryptopp, libcryptopp.so.

Comment 2 nucleo 2012-01-23 12:22:14 UTC

Reassigning to cabal-install.

Comment 3 nucleo 2012-01-23 12:53:03 UTC

http://groups.google.com/group/cryptopp-users/browse_thread/thread/3b316bcec601730e/2313449e8be8a932

Comment 4 Dag Odenhall 2012-01-23 15:41:27 UTC

In that case, it's a bug in upstream happstack-server not cabal-install.  The build specification [1] lists a dependency on "crypto++".  Now the question is, should Fedora try to be compatible with "debian innovations" when possible?

[1] http://hackage.haskell.org/packages/archive/happstack-server/6.5.1/happstack-server.cabal

Comment 5 nucleo 2012-01-23 15:57:14 UTC

(In reply to comment #4)
> Now the question is,
> should Fedora try to be compatible with "debian innovations" when possible?

No. Why we should repeat mistakes of other disro?
happstack-server should follow naming recommended by Crypto++ upstream.

Comment 6 Dag Odenhall 2012-01-23 16:55:57 UTC

Fixed in happstack-server-6.5.2.  Should I close this now?

Comment 7 nucleo 2012-01-23 17:35:38 UTC

(In reply to comment #6)
> Fixed in happstack-server-6.5.2.  Should I close this now?

I guess so, if it actually works.

Comment 8 Jens Petersen 2012-01-24 01:16:13 UTC

Ok thanks closing - I was just about to comment that you could patch
happstack-server.cabal for this - but good that has already
been upstreamed. :)