Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=425882 Summary: Review Request: ghc681-zlib - zlib bindings for ghc 6.8.1 Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: medium Priority: low Component: Package Review AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] CC: [email protected],[EMAIL PROTECTED] Spec URL: http://fedorapeople.org/~ynemoy/ghc681-zlib.spec SRPM URL: http://fedorapeople.org/~ynemoy/ghc681-zlib-0.4.0.1-1.fc8.src.rpm Description: zlib bindings for ghc 6.8.1 So admittedly this spec file worked better 5 minutes before i copied it than now, but This kinda sorta shows the direction I want to take with haskell packages. I am actually looking to enter in a bunch of Haskell packages into Fedora, but I want to figure out what is a good way of doing it in a general manner. Haskell has a large library of packages with package metadata, using a system called 'cabal' and hosting them in a central repository called 'hackagedb'. It is similar to CPAN or the Python Cheese Shop. There is also a package called cabal-rpm, that I would like to fix up, so that it can generate many packages that are also Fedora quality. There are a bunch of issues that need addressing. The biggest one is the naming scheme. Let's say a package has the name 'zlib' and it has two executables 'zlib' and 'zlib-setup'. It also has a library that in haskell is known as 'Zlib', but in the filesystem is saved as 'zlib'. It would require at bare minimum the following packages in Fedora: zlib.rpm --the executable ghc{ver}-zlib --the library ghc{ver}-zlib-prof --the profiling extras there might also be: zlib-doc --documentation for the binary only haskell-doc --documentation for the library's api, that is generic to any haskell compiler ghc{ver}-zlib-doc --documentation that is related to a specific compiler Ideally, I would like there to be a single spec for a library/program in Fedora for each compiler. cabal-rpm requires that the compiler be specified when generating the spec file, so I would like to parallel this sentiment. The spec file would generate at least a library package for each version of that compiler available in Fedora, where necessary. It would also create at least a binary compiled with the newest version of that compiler available, and perhaps a binary for other versions as well. In short, this is why the naming is messed up currently, as I'm not sure what is ultimately the best way to go about this. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. _______________________________________________ Fedora-package-review mailing list [email protected] http://www.redhat.com/mailman/listinfo/fedora-package-review
