public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ankur Sinha (Ankur Sinha Gmail) <sanjay.ankur@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libb64] epel10: Initial import
Date: Thu, 09 Jul 2026 18:31:33 GMT [thread overview]
Message-ID: <178362189303.1.11376195066125410438.rpms-libb64-e94c1ee84d54@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/libb64
Branch : epel10
Commit : e94c1ee84d54886047279515dbc51ac40ee690e8
Author : Ankur Sinha (Ankur Sinha Gmail) <sanjay.ankur@gmail.com>
Date : 2018-11-09T16:07:34+00:00
Stats : +94/-0 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/libb64/c/e94c1ee84d54886047279515dbc51ac40ee690e8?branch=epel10
Log:
Initial import
---
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..7c52ac0
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+/libb64-1.2.src.zip
diff --git a/libb64.spec b/libb64.spec
new file mode 100644
index 0000000..56f4d4b
--- /dev/null
+++ b/libb64.spec
@@ -0,0 +1,92 @@
+Name: libb64
+Version: 1.2
+Release: 3%{?dist}
+Summary: Tools for fast encoding/decoding data into and from a base64-encoded format
+
+License: Public Domain
+URL: http://libb64.sourceforge.net/
+Source0: https://downloads.sourceforge.net/%{name}/%{name}-%{version}.src.zip
+
+
+BuildRequires: gcc-c++
+
+%description
+Base64 uses a subset of displayable ASCII characters, and is therefore a useful
+encoding for storing binary data in a text file, such as XML, or sending binary
+data over text-only email.
+
+libb64 is a library of ANSI C routines for fast encoding/decoding data into and
+from a base64-encoded format. C++ wrappers are included, as well as the source
+code for standalone encoding and decoding executables.
+
+
+
+%package devel
+Summary: Development files for %{name}
+# Upstream only provides a static library
+Provides: %{name}-static = %{version}-%{release}
+# Does not need to require the base package as it is complete itself
+
+%description devel
+The %{name}-devel package contains the library and header files for developing
+applications that use %{name}.
+
+
+%package tools
+Summary: %{name}-b64 binary provided by %{name}
+
+%description tools
+This package provides the %{name}-b64 binary tool for encoding to and decoding
+from the Base64 scheme. Please install the %{name}-devel package to develop
+software using %{name}.
+
+%prep
+%autosetup
+
+# Remove unneeded flags
+sed -i '/-O3/ d' src/Makefile
+sed -i '/pedantic/ d' src/Makefile
+
+
+%build
+%set_build_flags
+%make_build
+
+
+%install
+# Upstream doesn't provide any install bits in the Makefile
+# static lib
+install -D -m 0644 -p src/libb64.a $RPM_BUILD_ROOT/%{_libdir}/libb64.a
+# binary, rename to prevent conflict with coreutils binary
+install -D -m 0755 -p base64/base64 $RPM_BUILD_ROOT/%{_bindir}/libb64-base64
+# headers
+install -D -m 0644 -p -t $RPM_BUILD_ROOT/%{_includedir}/b64/ include/b64/*
+
+# Only static, so we don't need ldconfig scriptlets
+
+
+%files tools
+%license LICENSE
+%doc AUTHORS README
+%{_bindir}/libb64-base64
+
+%files devel
+%license LICENSE
+%{_includedir}/b64
+%{_libdir}/libb64.a
+
+%changelog
+* Tue Nov 06 2018 Ankur Sinha <ankursinha AT fedoraproject DOT org> - 1.2-3
+- Move binary to -tools sub package
+- Rename binary to prevent conflict
+- Improve summary and description
+- Prevent addition to compiler flags
+- Do not require main package from devel
+- Do not use empty TODO file
+
+* Sun Nov 04 2018 Ankur Sinha <ankursinha AT fedoraproject DOT org> - 1.2-2
+- Do not use description macro
+- Use easier macro for build flags
+
+* Sat Nov 03 2018 Ankur Sinha <ankursinha AT fedoraproject DOT org> - 1.2-1
+- Initial build
diff --git a/sources b/sources
new file mode 100644
index 0000000..c408d45
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+SHA512 (libb64-1.2.src.zip) = ac041c78bf324a027e311fb10935886f8713f9b6ac53136396186a5b5fd936efdf6add715899827591bdf6d3727f6e27f680bc273c7634517cc2e1941140f596
reply other threads:[~2026-07-09 18:31 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=178362189303.1.11376195066125410438.rpms-libb64-e94c1ee84d54@fedoraproject.org \
--to=sanjay.ankur@gmail.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