public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jens Petersen <petersen@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/c2hs] epel9: import #1993600
Date: Mon, 13 Jul 2026 14:27:50 GMT [thread overview]
Message-ID: <178395287025.1.4452923721585887366.rpms-c2hs-cda0624f1307@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/c2hs
Branch : epel9
Commit : cda0624f13079f72cba7bd491a4c96a3d9fd7ed9
Author : Jens Petersen <petersen@redhat.com>
Date : 2023-08-04T15:55:41+01:00
Stats : +74/-0 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/c2hs/c/cda0624f13079f72cba7bd491a4c96a3d9fd7ed9?branch=epel9
Log:
import #1993600
---
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..2eac32c
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+/c2hs-0.28.8.tar.gz
diff --git a/c2hs.spec b/c2hs.spec
new file mode 100644
index 0000000..d71e468
--- /dev/null
+++ b/c2hs.spec
@@ -0,0 +1,72 @@
+# generated by cabal-rpm-2.0.10
+# https://docs.fedoraproject.org/en-US/packaging-guidelines/Haskell/
+
+# testsuite missing deps: test-framework test-framework-hunit
+
+Name: c2hs
+Version: 0.28.8
+Release: 1%{?dist}
+Summary: C->Haskell FFI tool that gives some cross-language type safety
+
+# Core code is GPL-2.0-or-later
+# but C2HS.hs is BSD-3-Clause
+# and src/Text/Lexers.hs is LGPL-2.1-or-later.
+License: BSD-3-Clause AND GPL-2.0-or-later AND LGPL-2.1-or-later
+Url: https://hackage.haskell.org/package/%{name}
+# Begin cabal-rpm sources:
+Source0: https://hackage.haskell.org/package/%{name}-%{version}/%{name}-%{version}.tar.gz
+# End cabal-rpm sources
+
+# Begin cabal-rpm deps:
+BuildRequires: ghc-Cabal-devel
+BuildRequires: ghc-rpm-macros
+BuildRequires: ghc-array-static
+BuildRequires: ghc-base-static
+BuildRequires: ghc-bytestring-static
+BuildRequires: ghc-containers-static
+BuildRequires: ghc-directory-static
+BuildRequires: ghc-dlist-static
+BuildRequires: ghc-filepath-static
+BuildRequires: ghc-language-c-static
+BuildRequires: ghc-pretty-static
+BuildRequires: ghc-process-static
+# End cabal-rpm deps
+
+%description
+C->Haskell assists in the development of Haskell bindings to C libraries.
+It extracts interface information from C header files and generates Haskell
+code with foreign imports and marshaling. Unlike writing foreign imports by
+hand (or using hsc2hs), this ensures that C functions are imported with the
+correct Haskell types.
+
+
+%prep
+# Begin cabal-rpm setup:
+%setup -q
+# End cabal-rpm setup
+
+
+%build
+# Begin cabal-rpm build:
+%ghc_bin_build
+# End cabal-rpm build
+
+
+%install
+# Begin cabal-rpm install
+%ghc_bin_install
+# End cabal-rpm install
+
+
+%files
+# Begin cabal-rpm files:
+%license COPYING
+%doc AUTHORS ChangeLog ChangeLog.old README
+%{_bindir}/%{name}
+%{_datadir}/%{name}-%{version}
+# End cabal-rpm files
+
+
+%changelog
+* Fri Aug 13 2021 Jens Petersen <petersen@redhat.com> - 0.28.8-1
+- spec file generated by cabal-rpm-2.0.10
diff --git a/sources b/sources
new file mode 100644
index 0000000..17a84da
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+SHA512 (c2hs-0.28.8.tar.gz) = ff9119acecddd853f2f797385f971c249bcd92d4b141e8e7ea5f5d3e63aa257502c80ded2720a46e3186260026b94c9e518f08f8e452a64c9f888d0183ee1749
reply other threads:[~2026-07-13 14:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178395287025.1.4452923721585887366.rpms-c2hs-cda0624f1307@fedoraproject.org \
--to=petersen@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox