diff --git a/minitest-5.14.4.gem b/minitest-5.14.4.gem
new file mode 100644
index 0000000000000000000000000000000000000000..6a7369480468ddf84e4e2d18ae4495030d533cdd
Binary files /dev/null and b/minitest-5.14.4.gem differ
diff --git a/rubygem-minitest.spec b/rubygem-minitest.spec
new file mode 100644
index 0000000000000000000000000000000000000000..4df4f1e13667e74718eb256c37ec3cb55048ab66
--- /dev/null
+++ b/rubygem-minitest.spec
@@ -0,0 +1,95 @@
+# Generated from minitest-1.4.2.gem by gem2rpm -*- rpm-spec -*-
+%global gem_name minitest
+
+Name: rubygem-%{gem_name}
+Version: 5.14.4
+Release: 1
+Summary: minitest provides a complete suite of testing facilities
+License: MIT
+URL: https://github.com/seattlerb/minitest
+Source0: https://rubygems.org/gems/%{gem_name}-%{version}.gem
+BuildRequires: ruby(release) rubygems-devel
+BuildArch: noarch
+
+%description
+minitest provides a complete suite of testing facilities supporting
+TDD, BDD, mocking, and benchmarking.
+
+minitest/unit is a small and incredibly fast unit testing framework.
+It provides a rich set of assertions to make your tests clean and
+readable.
+
+minitest/spec is a functionally complete spec engine. It hooks onto
+minitest/unit and seamlessly bridges test assertions over to spec
+expectations.
+
+minitest/benchmark is an awesome way to assert the performance of your
+algorithms in a repeatable manner. Now you can assert that your newb
+co-worker doesn't replace your linear algorithm with an exponential
+one!
+
+minitest/mock by Steven Baker, is a beautifully tiny mock (and stub)
+object framework.
+
+minitest/pride shows pride in testing and adds coloring to your test
+output. I guess it is an example of how to write IO pipes too. :P
+minitest/unit is meant to have a clean implementation for language
+implementors that need a minimal set of methods to bootstrap a working
+test suite. For example, there is no magic involved for test-case
+discovery.
+
+minitest doesn't reinvent anything that ruby already provides, like:
+classes, modules, inheritance, methods. This means you only have to
+learn ruby to use minitest and all of your regular OO practices like
+extract-method refactorings still apply.
+
+
+%package doc
+Summary: Documentation for %{name}
+Requires: %{name} = %{version}-%{release}
+BuildArch: noarch
+
+%description doc
+Documentation for %{name}.
+
+%prep
+%setup -q -n %{gem_name}-%{version}
+mv ../%{gem_name}-%{version}.gemspec .
+
+%build
+gem build %{gem_name}-%{version}.gemspec
+%gem_install
+
+%install
+mkdir -p %{buildroot}%{gem_dir}
+cp -a .%{gem_dir}/* \
+        %{buildroot}%{gem_dir}/
+
+%check
+LANG=C.UTF-8
+LC_ALL=C.utf8
+pushd .%{gem_instdir}
+
+ruby -Ilib:test -e 'Dir.glob "./test/minitest/test_*.rb", &method(:require)'
+
+popd
+
+%files
+%doc %{gem_instdir}/README.rdoc
+%dir %{gem_instdir}
+%exclude %{gem_instdir}/.*
+%{gem_libdir}
+%exclude %{gem_cache}
+%{gem_spec}
+
+%files doc
+%doc %{gem_docdir}
+%doc %{gem_instdir}/History.rdoc
+%doc %{gem_instdir}/Manifest.txt
+%exclude %{gem_instdir}/Rakefile
+%exclude %{gem_instdir}/test
+%{gem_instdir}/design_rationale.rb
+
+%changelog
+* Mon Dec 27 2021 lipanpan <lipanpana@uniontech.com> - 5.14.4
+- package init
\ No newline at end of file