2015-07-15 17:02:34 +00:00
|
|
|
#
|
|
|
|
|
# spec file for package tint2
|
|
|
|
|
#
|
2024-02-23 14:47:41 +00:00
|
|
|
# Copyright (c) 2024 SUSE LLC
|
2015-07-15 17:02:34 +00:00
|
|
|
#
|
|
|
|
|
# All modifications and additions to the file contributed by third parties
|
|
|
|
|
# remain the property of their copyright owners, unless otherwise agreed
|
|
|
|
|
# upon. The license for this file, and modifications and additions to the
|
|
|
|
|
# file, is the same license as for the pristine package itself (unless the
|
|
|
|
|
# license for the pristine package is not an Open Source License, in which
|
|
|
|
|
# case the license is the MIT License). An "Open Source License" is a
|
|
|
|
|
# license that conforms to the Open Source Definition (Version 1.9)
|
|
|
|
|
# published by the Open Source Initiative.
|
|
|
|
|
|
2021-06-07 14:29:22 +00:00
|
|
|
# Please submit bugfixes or comments via https://bugs.opensuse.org/
|
2015-07-15 17:02:34 +00:00
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Name: tint2
|
2024-02-23 14:47:41 +00:00
|
|
|
Version: 17.1.3
|
2015-07-15 17:02:34 +00:00
|
|
|
Release: 0
|
|
|
|
|
Summary: A lightweight X11 desktop panel and task manager
|
2021-04-15 14:40:34 +00:00
|
|
|
License: GPL-2.0-only
|
|
|
|
|
Group: System/X11/Utilities
|
2024-02-23 14:47:41 +00:00
|
|
|
URL: https://gitlab.com/nick87720z/tint2
|
|
|
|
|
Source0: https://gitlab.com/nick87720z/%{name}/-/archive/v%{version}/%{name}-v%{version}.tar.bz2
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
Source1: tint2conf.1
|
2015-07-15 17:02:34 +00:00
|
|
|
BuildRequires: cmake
|
|
|
|
|
BuildRequires: desktop-file-utils
|
|
|
|
|
BuildRequires: gcc-c++
|
|
|
|
|
BuildRequires: gettext
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
BuildRequires: pkgconfig
|
|
|
|
|
BuildRequires: pkgconfig(cairo)
|
2021-06-07 14:29:22 +00:00
|
|
|
BuildRequires: pkgconfig(gtk+-x11-3.0)
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
BuildRequires: pkgconfig(imlib2)
|
|
|
|
|
BuildRequires: pkgconfig(librsvg-2.0)
|
|
|
|
|
BuildRequires: pkgconfig(libstartup-notification-1.0)
|
|
|
|
|
BuildRequires: pkgconfig(pango)
|
|
|
|
|
BuildRequires: pkgconfig(pangocairo)
|
2021-06-07 14:29:22 +00:00
|
|
|
BuildRequires: pkgconfig(x11)
|
|
|
|
|
BuildRequires: pkgconfig(xcomposite)
|
|
|
|
|
BuildRequires: pkgconfig(xdamage)
|
|
|
|
|
BuildRequires: pkgconfig(xext)
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
BuildRequires: pkgconfig(xinerama)
|
2021-06-07 14:29:22 +00:00
|
|
|
BuildRequires: pkgconfig(xrandr)
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
BuildRequires: pkgconfig(xrender)
|
2015-07-15 17:02:34 +00:00
|
|
|
|
|
|
|
|
%description
|
|
|
|
|
tint2 is a simple panel/taskbar made for modern X window managers. It was
|
|
|
|
|
specifically made for Openbox3 but should also work with other window managers.
|
|
|
|
|
|
|
|
|
|
%lang_package
|
|
|
|
|
|
|
|
|
|
%prep
|
2024-02-23 14:47:41 +00:00
|
|
|
%autosetup -n %{name}-v%{version}
|
2015-07-15 17:02:34 +00:00
|
|
|
|
|
|
|
|
%build
|
2021-06-07 14:29:22 +00:00
|
|
|
%cmake -DCMAKE_INSTALL_DOCDIR=%{_defaultdocdir}/%{name}
|
|
|
|
|
%cmake_build
|
2015-07-15 17:02:34 +00:00
|
|
|
|
|
|
|
|
%install
|
|
|
|
|
%cmake_install
|
|
|
|
|
|
|
|
|
|
# create tint2 config directory
|
2024-02-23 14:47:41 +00:00
|
|
|
#mkdir -p %{buildroot}%{_sysconfdir}/skel/.config/tint2/
|
2015-07-15 17:02:34 +00:00
|
|
|
|
|
|
|
|
desktop-file-install \
|
|
|
|
|
--set-key=NoDisplay --set-value=true \
|
|
|
|
|
--delete-original \
|
|
|
|
|
--dir=%{buildroot}%{_datadir}/applications \
|
|
|
|
|
%{buildroot}/%{_datadir}/applications/tint2.desktop
|
|
|
|
|
|
|
|
|
|
desktop-file-install \
|
|
|
|
|
--delete-original \
|
|
|
|
|
--dir=%{buildroot}%{_datadir}/applications \
|
|
|
|
|
%{buildroot}/%{_datadir}/applications/tint2conf.desktop
|
|
|
|
|
|
2021-04-15 14:40:34 +00:00
|
|
|
# install man page for tint2conf (written for Debian package)
|
|
|
|
|
install -m 0644 %{SOURCE1} %{buildroot}/%{_mandir}/man1/
|
|
|
|
|
|
2015-07-15 17:02:34 +00:00
|
|
|
%find_lang tint2conf
|
|
|
|
|
|
|
|
|
|
%files
|
2021-06-07 14:29:22 +00:00
|
|
|
%license COPYING
|
|
|
|
|
%doc AUTHORS CONTRIBUTING.md ChangeLog README.md
|
|
|
|
|
%doc %{_defaultdocdir}/tint2/
|
2024-02-23 14:47:41 +00:00
|
|
|
#%dir %{_sysconfdir}/skel/.config/
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
%dir %{_sysconfdir}/xdg/tint2
|
2021-06-07 14:29:22 +00:00
|
|
|
%config(noreplace) %{_sysconfdir}/xdg/tint2/tint2rc
|
2024-02-23 14:47:41 +00:00
|
|
|
#%{_sysconfdir}/skel/.config/tint2/
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
%{_bindir}/tint2
|
2024-02-23 14:47:41 +00:00
|
|
|
%{_bindir}/tint2-send
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
%{_bindir}/tint2conf
|
2015-07-15 17:02:34 +00:00
|
|
|
%{_datadir}/tint2/
|
|
|
|
|
%{_datadir}/applications/tint2conf.desktop
|
|
|
|
|
%{_datadir}/applications/tint2.desktop
|
|
|
|
|
%{_datadir}/icons/hicolor/*/apps/tint*
|
2021-04-15 14:40:34 +00:00
|
|
|
%{_datadir}/mime/packages/tint2conf.xml
|
- Update to 3.6.0:
Breaking:
* We added the backslash escape character (\) for configuration values. This
means that the literal backslash character now has special meaning in
configuration files, therefore if you want to use it in a value as a literal
backslash, you need to escape it with the backslash escape character. The parser
logs an error if any unescaped backslashes are found in a value. This affects
you only if you are using two consecutive backslashes in a config value, which
will now be interpreted as a single literal backslash. (#2354)
* We rewrote our formatting tag parser. This shouldn't break anything, if you
experience any problems, please let us know. The new parser now gives errors for
certain invalid tags where the old parser would just silently ignore them.
Adding extra text to the end of a valid tag now produces an error. For example,
tags like %{T-a}, %{T2abc}, %{rfoo}, and others will now start producing errors.
This does not affect you unless you are producing your own invalid formatting
tags (for example in a script).
* For security reasons, the named pipe at /tmp/polybar_mqueue.<PID> had its
permission bits changed from 666 to 600 to prevent sending ipc messages to
polybar processes running under a different user.
* For details see: https://github.com/polybar/polybar/releases/tag/3.6.0
OBS-URL: https://build.opensuse.org/package/show/X11:Utilities/tint2?expand=0&rev=37
2022-03-03 08:38:34 +00:00
|
|
|
%{_mandir}/man1/tint*.1%{?ext_man}
|
2015-07-15 17:02:34 +00:00
|
|
|
|
|
|
|
|
%files lang -f tint2conf.lang
|
2021-04-15 14:40:34 +00:00
|
|
|
|
|
|
|
|
%changelog
|
