Archives
/
notcurses
mirror of https://github.com/dankamongmen/notcurses
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
mouse-demo
dankamongmen/mosaicworld
dankamongmen/unibilium
dankamongmen/octrees-for-victory
gh-pages
dankamongmen/windows-tester
dankamongmen/pile-drop-graphics
dankamongmen/DRMmeharder
dankamongmen/fbconscrollamatic
dankamongmen/iterm2complete
dankamongmen/linuxfbdumb
dankamongmen/rationalize-rgba
dankamongmen/thirdpass
dankamongmen/libsixel
dankamongmen/sixel-quantize
dankamongmen/sixel-speedup
dankamongmen/libvlc
dankamongmen/split-em-up
dankamongmen/ltr
dankamongmen/clock_nanosleep_portable
dankamongmen/xcb
github-action
dankamongmen/speedypainter
dankamongmen/slickgoose
dankamongmen/speedy-blend
v3.0.11
v3.0.10
v3.0.9
v3.0.8
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v2.4.9
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.4
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.18
v2.3.17
v2.3.16
v2.3.15
v2.3.14
v2.3.13
v2.3.12
v2.3.11
v2.3.10
v2.3.9
v2.3.8
v2.3.7
v2.3.6
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.11
v2.2.10
v2.2.9
v2.2.8
v2.2.7
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.8
v2.1.7
v2.1.5
v2.1.4
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.12
v2.0.11
v2.0.10
v2.0.9
v2.0.8
v2.0.7
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.7.6
v1.7.5
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.6.20
v1.6.19
v1.6.17
v1.6.15
v1.6.12
v1.6.11
v1.6.10
v1.6.9
v1.6.6
v1.6.3
v1.6.1
v1.6.0
v1.5.3
v1.5.2
v1.5.1
v1.5.0
v1.4.5
v1.4.4.1
v1.4.3
v1.4.2.4
v1.4.2.3
v1.4.1
v1.4.0
v1.3.4
v1.3.3
v1.3.2
v1.3.1
v1.3.0
v1.2.9
v1.2.8
v1.2.7
v1.2.6
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.9
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.4.0
v0.3.0
v0.2.0
v0.1.0
v0.0.9
v1.6.18
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9577c4afa0'
${ noResults }
notcurses/tools/notcurses.spec

135 lines
4.0 KiB
Plaintext
Raw Normal View History Unescape Escape

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.
5 years ago
Name: notcurses
prep for 1.2.7
5 years ago
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.
5 years ago
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
fedora: fix path for package signature
5 years ago
Source1: https://github.com/dankamongmen/%{name}/releases/download/v%{version}/v%{version}.tar.gz.asc
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.
5 years ago
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
5 years ago
%description
notcurses facilitates the creation of modern TUI programs,
s/direct color/TrueColor/g
5 years ago
making full use of Unicode and 24-bit TrueColor. 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
5 years ago
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
5 years ago
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.
5 years ago
%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
5 years ago
%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.
5 years ago
%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
5 years ago
%build
fedora: USE_TESTS in specfile, not USE_TEST, ugh
5 years ago
%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
5 years ago
%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.
5 years ago
%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
fedora: add ncpp include files to package
5 years ago
%{_includedir}/ncpp/Cell.hh
%{_includedir}/ncpp/CellStyle.hh
%{_includedir}/ncpp/Direct.hh
%{_includedir}/ncpp/Menu.hh
%{_includedir}/ncpp/MultiSelector.hh
%{_includedir}/ncpp/NCAlign.hh
%{_includedir}/ncpp/NCBox.hh
%{_includedir}/ncpp/NCKey.hh
%{_includedir}/ncpp/NCLogLevel.hh
%{_includedir}/ncpp/NCScale.hh
%{_includedir}/ncpp/NotCurses.hh
%{_includedir}/ncpp/Palette256.hh
%{_includedir}/ncpp/Plane.hh
%{_includedir}/ncpp/Plot.hh
%{_includedir}/ncpp/Reel.hh
%{_includedir}/ncpp/Root.hh
%{_includedir}/ncpp/Selector.hh
%{_includedir}/ncpp/Tablet.hh
%{_includedir}/ncpp/TabletCallback.hh
%{_includedir}/ncpp/Visual.hh
%{_includedir}/ncpp/_exceptions.hh
%{_includedir}/ncpp/_flag_enum_operator_helpers.hh
%{_includedir}/ncpp/_helpers.hh
%{_includedir}/ncpp/internal
%{_includedir}/ncpp/internal/Helpers.hh
%{_includedir}/ncpp/ncpp.hh
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.
5 years ago
%{_libdir}/libnotcurses.so
%{_libdir}/libnotcurses++.so
%{_libdir}/cmake/notcurses
%{_libdir}/pkgconfig/notcurses.pc
%{_libdir}/pkgconfig/notcurses++.pc
%{_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
fedora: fix specfile notcurses-tetris.1.gz path
5 years ago
%{_mandir}/man1/notcurses-tetris.1.gz
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.
5 years ago
%{_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
5 years ago
%changelog
prep for 1.2.7
5 years ago
* 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
5 years ago
- Initial Fedora packaging