Archives/notcurses
2
0
Fork 0
mirror of https://github.com/dankamongmen/notcurses.git synced 2024-11-02 09:40:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
e005940acf
notcurses/tools/notcurses.spec

110 lines
3.3 KiB
RPMSpec
Raw Normal View History

Change notcurses.spec to follow Fedora Packaging Policy More or less. Here's a list of things I changed: * Single line BuildRequires which is more of a convention than a requirement. * Drop make from BuildRequires. That's one we do actually provide. * Use pkgconfig(ncurses) to get the ncurses-devel BuildRequires. * Add a 'devel' subject and move development files there. * Add a 'static' package for the .a libraries which is common for other packages that provide static libraries. * Add doc files using %doc * -DUSE_TEST=off -> -DUSE_TESTS=off * Use %autosetup in %setup which covers adding patches in the future for downstream packaging. * Use path macros in %files * Correct the date format in the %changelog entry * Use the 1.2.6 release as an example Things that could use more consideration: * The release artifacts don't match what GitHub provides. Their automated download link gives you notcurses-1.2.6.tar.gz but the URL calls it v1.2.6.tar.gz. * There is no signature file uploaded. * notcurses-tester and notcurses-viewer do not build. * Should the demo programs go in the main package or devel. I felt devel was more appropriate. * Should the packaging be further refined to split out the C++ runtime and static libraries to separate subpackages? I did some local test runs using mock. I ran the SRPM through rpmlint which would happen when the package is submitted for inclusion. For the download archive and signature, I create new release posts on my github projects and create a separate tarball and sign that and upload them there. It is separate from the GitHub automated make-me-a-tarball download link. That might be what you're planning on doing.
2020-04-08 14:43:48 +00:00
Name: notcurses
prep for 1.2.7
2020-04-10 00:21:33 +00:00
Version: 1.2.7
Change notcurses.spec to follow Fedora Packaging Policy More or less. Here's a list of things I changed: * Single line BuildRequires which is more of a convention than a requirement. * Drop make from BuildRequires. That's one we do actually provide. * Use pkgconfig(ncurses) to get the ncurses-devel BuildRequires. * Add a 'devel' subject and move development files there. * Add a 'static' package for the .a libraries which is common for other packages that provide static libraries. * Add doc files using %doc * -DUSE_TEST=off -> -DUSE_TESTS=off * Use %autosetup in %setup which covers adding patches in the future for downstream packaging. * Use path macros in %files * Correct the date format in the %changelog entry * Use the 1.2.6 release as an example Things that could use more consideration: * The release artifacts don't match what GitHub provides. Their automated download link gives you notcurses-1.2.6.tar.gz but the URL calls it v1.2.6.tar.gz. * There is no signature file uploaded. * notcurses-tester and notcurses-viewer do not build. * Should the demo programs go in the main package or devel. I felt devel was more appropriate. * Should the packaging be further refined to split out the C++ runtime and static libraries to separate subpackages? I did some local test runs using mock. I ran the SRPM through rpmlint which would happen when the package is submitted for inclusion. For the download archive and signature, I create new release posts on my github projects and create a separate tarball and sign that and upload them there. It is separate from the GitHub automated make-me-a-tarball download link. That might be what you're planning on doing.
2020-04-08 14:43:48 +00:00
Release: 1%{?dist}
Summary: Character graphics and TUI library
License: ASL 2.0
URL: https://nick-black.com/dankwiki/index.php/Notcurses
Source0: https://github.com/dankamongmen/%{name}/archive/v%{version}.tar.gz
Source1: https://github.com/dankamongmen/%{name}/releases/v%{version}/v%{version}.tar.gz.asc
Source2: https://dank.qemfd.net/dankamongmen.gpg
BuildRequires: gnupg2
BuildRequires: cmake
BuildRequires: gcc-c++
BuildRequires: pandoc
BuildRequires: python3-devel
BuildRequires: pkgconfig(ncurses)
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
%description
notcurses facilitates the creation of modern TUI programs,
making full use of Unicode and 24-bit direct color. It presents
Rust wrapper work (#454) * packaging: s/libtinfo/Terminfo/g * rust: add stddim_yx() * rust: check for valid init in unit tests * rust: serialize up tests * constify notcurses_term_dim_yx() * rust: add dim wrappers * remove notcurses_resize() from public API #367 * call notcurses_resize() from notcurses_refresh() #367
2020-04-08 09:39:41 +00:00
an API similar to that of Curses, and rides atop Terminfo.
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
Change notcurses.spec to follow Fedora Packaging Policy More or less. Here's a list of things I changed: * Single line BuildRequires which is more of a convention than a requirement. * Drop make from BuildRequires. That's one we do actually provide. * Use pkgconfig(ncurses) to get the ncurses-devel BuildRequires. * Add a 'devel' subject and move development files there. * Add a 'static' package for the .a libraries which is common for other packages that provide static libraries. * Add doc files using %doc * -DUSE_TEST=off -> -DUSE_TESTS=off * Use %autosetup in %setup which covers adding patches in the future for downstream packaging. * Use path macros in %files * Correct the date format in the %changelog entry * Use the 1.2.6 release as an example Things that could use more consideration: * The release artifacts don't match what GitHub provides. Their automated download link gives you notcurses-1.2.6.tar.gz but the URL calls it v1.2.6.tar.gz. * There is no signature file uploaded. * notcurses-tester and notcurses-viewer do not build. * Should the demo programs go in the main package or devel. I felt devel was more appropriate. * Should the packaging be further refined to split out the C++ runtime and static libraries to separate subpackages? I did some local test runs using mock. I ran the SRPM through rpmlint which would happen when the package is submitted for inclusion. For the download archive and signature, I create new release posts on my github projects and create a separate tarball and sign that and upload them there. It is separate from the GitHub automated make-me-a-tarball download link. That might be what you're planning on doing.
2020-04-08 14:43:48 +00:00
%package devel
Summary: Development files for the notcurses library
License: ASL 2.0
Requires: %{name} = %{version}-%{release}
%description devel
This package contains the development files for the notcurses
library.
%package static
Summary: Static library for the notcurses library
License: ASL 2.0
Requires: %{name}-devel = %{version}-%{release}
%description static
The notcurses-static package includes the static notcurses library.
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
%prep
%{gpgverify} --keyring='%{SOURCE2}' --signature='%{SOURCE1}' --data='%{SOURCE0}'
Change notcurses.spec to follow Fedora Packaging Policy More or less. Here's a list of things I changed: * Single line BuildRequires which is more of a convention than a requirement. * Drop make from BuildRequires. That's one we do actually provide. * Use pkgconfig(ncurses) to get the ncurses-devel BuildRequires. * Add a 'devel' subject and move development files there. * Add a 'static' package for the .a libraries which is common for other packages that provide static libraries. * Add doc files using %doc * -DUSE_TEST=off -> -DUSE_TESTS=off * Use %autosetup in %setup which covers adding patches in the future for downstream packaging. * Use path macros in %files * Correct the date format in the %changelog entry * Use the 1.2.6 release as an example Things that could use more consideration: * The release artifacts don't match what GitHub provides. Their automated download link gives you notcurses-1.2.6.tar.gz but the URL calls it v1.2.6.tar.gz. * There is no signature file uploaded. * notcurses-tester and notcurses-viewer do not build. * Should the demo programs go in the main package or devel. I felt devel was more appropriate. * Should the packaging be further refined to split out the C++ runtime and static libraries to separate subpackages? I did some local test runs using mock. I ran the SRPM through rpmlint which would happen when the package is submitted for inclusion. For the download archive and signature, I create new release posts on my github projects and create a separate tarball and sign that and upload them there. It is separate from the GitHub automated make-me-a-tarball download link. That might be what you're planning on doing.
2020-04-08 14:43:48 +00:00
%autosetup
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
%build
fedora: USE_TESTS in specfile, not USE_TEST, ugh
2020-04-08 15:46:33 +00:00
%cmake -DUSE_FFMPEG=off -DUSE_TESTS=off .
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
%make_build
%install
%make_install
%files
Change notcurses.spec to follow Fedora Packaging Policy More or less. Here's a list of things I changed: * Single line BuildRequires which is more of a convention than a requirement. * Drop make from BuildRequires. That's one we do actually provide. * Use pkgconfig(ncurses) to get the ncurses-devel BuildRequires. * Add a 'devel' subject and move development files there. * Add a 'static' package for the .a libraries which is common for other packages that provide static libraries. * Add doc files using %doc * -DUSE_TEST=off -> -DUSE_TESTS=off * Use %autosetup in %setup which covers adding patches in the future for downstream packaging. * Use path macros in %files * Correct the date format in the %changelog entry * Use the 1.2.6 release as an example Things that could use more consideration: * The release artifacts don't match what GitHub provides. Their automated download link gives you notcurses-1.2.6.tar.gz but the URL calls it v1.2.6.tar.gz. * There is no signature file uploaded. * notcurses-tester and notcurses-viewer do not build. * Should the demo programs go in the main package or devel. I felt devel was more appropriate. * Should the packaging be further refined to split out the C++ runtime and static libraries to separate subpackages? I did some local test runs using mock. I ran the SRPM through rpmlint which would happen when the package is submitted for inclusion. For the download archive and signature, I create new release posts on my github projects and create a separate tarball and sign that and upload them there. It is separate from the GitHub automated make-me-a-tarball download link. That might be what you're planning on doing.
2020-04-08 14:43:48 +00:00
%doc CHANGELOG.md README.md
%license COPYRIGHT LICENSE
%{_libdir}/libnotcurses.so.%{version}
%{_libdir}/libnotcurses.so.1
%{_libdir}/libnotcurses++.so.1
%{_libdir}/libnotcurses++.so.%{version}
%files devel
%{_bindir}/notcurses-demo
%{_bindir}/notcurses-input
%{_bindir}/notcurses-ncreel
%{_bindir}/notcurses-pydemo
%{_bindir}/notcurses-tetris
%{_includedir}/notcurses/nckeys.h
%{_includedir}/notcurses/notcurses.h
%{_libdir}/libnotcurses.so
%{_libdir}/libnotcurses++.so
%{_libdir}/cmake/notcurses
%{_libdir}/pkgconfig/notcurses.pc
%{_libdir}/pkgconfig/notcurses++.pc
%{_mandir}/man1/colloquy.1.gz
%{_mandir}/man1/notcurses-demo.1.gz
%{_mandir}/man1/notcurses-input.1.gz
%{_mandir}/man1/notcurses-ncreel.1.gz
%{_mandir}/man1/notcurses-pydemo.1.gz
%{_mandir}/man1/notcurses-tester.1.gz
%{_mandir}/man/man1/notcurses-tetris.1.gz
%{_mandir}/man1/notcurses-view.1.gz
%{_mandir}/man3/notcurses.3.gz
%{_mandir}/man3/notcurses_cell.3.gz
%{_mandir}/man3/notcurses_channels.3.gz
%{_mandir}/man3/notcurses_directmode.3.gz
%{_mandir}/man3/notcurses_fade.3.gz
%{_mandir}/man3/notcurses_init.3.gz
%{_mandir}/man3/notcurses_input.3.gz
%{_mandir}/man3/notcurses_lines.3.gz
%{_mandir}/man3/notcurses_menu.3.gz
%{_mandir}/man3/notcurses_multiselector.3.gz
%{_mandir}/man3/notcurses_ncplane.3.gz
%{_mandir}/man3/notcurses_ncvisual.3.gz
%{_mandir}/man3/notcurses_output.3.gz
%{_mandir}/man3/notcurses_palette.3.gz
%{_mandir}/man3/notcurses_plot.3.gz
%{_mandir}/man3/notcurses_reel.3.gz
%{_mandir}/man3/notcurses_refresh.3.gz
%{_mandir}/man3/notcurses_render.3.gz
%{_mandir}/man3/notcurses_selector.3.gz
%{_mandir}/man3/notcurses_stats.3.gz
%{_mandir}/man3/notcurses_stdplane.3.gz
%{_mandir}/man3/notcurses_stop.3.gz
%files static
%{_libdir}/libnotcurses.a
%{_libdir}/libnotcurses++.a
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
%changelog
prep for 1.2.7
2020-04-10 00:21:33 +00:00
* Tue Apr 07 2020 Nick Black <dankamongmen@gmail.com> - 1.2.7-1
Prep for Fedora packaging (#452) * jungle demo should be available outside of DFSG builds * libav: blitters don't need FFMpeg * CMake: threads independent of ffmpeg * CMake: add USE_TESTS option to disable tests #450 * tetris: work without ffmpeg * fedora: flesh out specfile #328 * menu poc: don't use ffmpeg at all * compile PoCs with binary/include * multiselect PoC: work without ffmpeg
2020-04-08 06:12:46 +00:00
- Initial Fedora packaging
Reference in New Issue Copy Permalink