File _service:tar_git:sailfishos-chum-repo-config.spec of Package sailfishos-chum-repo-config

Summary:        SSU configuration for the SailfishOS:Chum community repository
License:        MIT
Name:           sailfishos-chum-repo-config
Version:    0.6.3
Release:        1
# The Group tag should comprise one of the groups listed here:
# https://github.com/mer-tools/spectacle/blob/master/data/GROUPS
Group:          Software Management/Package Manager
BuildArch:      noarch
URL:            https://github.com/sailfishos-chum/%{name}
Vendor:         chum
# The "Source0:" line below requires that the value of %%{name} is also the
# project name at GitHub and the value of %%{version} is also the name of a
# correspondingly set git-tag.
Source0:        %{url}/archive/%{version}/%{name}-%{version}.tar.gz
# Note that the rpmlintrc file shall be named so according to
# https://en.opensuse.org/openSUSE:Packaging_checks#Building_Packages_in_spite_of_errors
Source99:       %{name}.rpmlintrc
Requires:       ssu
Requires(post): ssu
Requires(postun): ssu
Conflicts:      sailfishos-chum-repo-config-testing
Obsoletes:      sailfishos-chum-repo-config-testing
Conflicts:      sailfishos-chum-testing
Obsoletes:      sailfishos-chum-testing
Conflicts:      sailfishos-chum
Obsoletes:      sailfishos-chum
Conflicts:      sailfishos-chum-gui
Conflicts:      sailfishos-chum-gui-installer
Provides:       sailfishos-chum-repository

%description
The package sailfishos-chum is a helper RPM, which solely provides an
appropriate local repository configuration for utilising the SailfishOS:Chum
community repository with command line tools as pkcon or zypper.

Note that the SailfishOS:Chum GUI application provides the same local
repository configuration, while also providing a GUI app, which can be used in
addition to pkcon or zypper.  Furthermore it offers easy switching between the
regular SailfishOS:Chum repository and the SailfishOS:Chum:Testing repository.
Hence you might rather install the sailfishos-chum-gui RPM (e.g., via the
sailfishos-chum-gui-installer RPM), instead of the sailfishos-chum RPM.

%if 0%{?_chum}
Title: SailfishOS:Chum repository configuration RPM
Type: generic
Categories:
 - System
 - Utility
 - Settings
 - PackageManager
 - ConsoleOnly
DeveloperName: SailfishOS:Chum community
Custom:
  Repo: %{url}
PackageIcon: %{url}/raw/main/.icons/sailfishos-chum.svg
Links:
  Homepage: https://openrepos.net/content/olf/sailfishoschum-repo-config-rpm
  Help: %{url}/issues
  Bugtracker: %{url}/issues
%endif

%package testing
Summary:        SSU configuration for the SailfishOS:Chum:Testing repository
License:        MIT
Group:          System
BuildArch:      noarch
Requires:       ssu
Requires(post): ssu
Requires(postun): ssu
Conflicts:      sailfishos-chum-repo-config
Obsoletes:      sailfishos-chum-repo-config
Conflicts:      sailfishos-chum
Obsoletes:      sailfishos-chum
Conflicts:      sailfishos-chum-testing
Obsoletes:      sailfishos-chum-testing
Conflicts:      sailfishos-chum-gui
Conflicts:      sailfishos-chum-gui-installer
Provides:       sailfishos-chum-repository

%description testing
The package sailfishos-chum-testing is a helper RPM, which solely provides an
appropriate local repository configuration for utilising the 
SailfishOS:Chum:Testing repository with command line tools as pkcon or zypper.
Note that the SailfishOS:Chum:Testing repository is primarily aimed at
software developers.

Also note that the SailfishOS:Chum GUI application provides the same local
repository configuration, while also providing a GUI app, which can be used in
addition to pkcon or zypper.  Furthermore it offers easy switching between the
regular SailfishOS:Chum repository and the SailfishOS:Chum:Testing repository.
Hence you might rather install the sailfishos-chum-gui RPM (e.g., via the
sailfishos-chum-gui-installer RPM), instead of the sailfishos-chum-testing RPM.

%if 0%{?_chum}
PackageName: SailfishOS:Chum:Testing repository configuration RPM
Type: generic
Categories:
 - System
 - Utility
 - Settings
 - PackageManager
 - ConsoleOnly
DeveloperName: SailfishOS:Chum community
Custom:
  Repo: %{url}
Icon: %{url}/raw/main/.icons/sailfishos-chum.svg
Url:
  Homepage: https://openrepos.net/content/olf/sailfishoschumtesting-repo-config-rpm
  Help: %{url}/issues
  Bugtracker: %{url}/issues
%endif

%define _binary_payload w6.gzdio
%define _source_payload w6.gzdio

%prep
%setup -q

%build

%install

%files

%files testing

%post
ssu ar sailfishos-chum 'https://repo.sailfishos.org/obs/sailfishos:/chum/%%(release)_%%(arch)/'
ssu ur
exit 0

%post testing
ssu ar sailfishos-chum-testing 'https://repo.sailfishos.org/obs/sailfishos:/chum:/testing/%%(release)_%%(arch)/'
ssu ur
exit 0

%postun
if [ "$1" = 0 ]  # Removal
then
  ssu rr sailfishos-chum
  rm -f /var/cache/ssu/features.ini
  ssu ur
fi
exit 0

%postun testing
if [ "$1" = 0 ]  # Removal
then
  ssu rr sailfishos-chum-testing
  rm -f /var/cache/ssu/features.ini
  ssu ur
fi
exit 0

# BTW, `ssu`, `rm -f`, `mkdir -p` etc. *always* return with "0" ("success"), hence
# no appended `|| true` needed to satisfy `set -e` for failing commands outside of
# flow control directives (if, while, until etc.).  Furthermore on Fedora Docs it
# is indicated that solely the final exit status of a whole scriptlet is crucial: 
# See https://docs.pagure.org/packaging-guidelines/Packaging%3AScriptlets.html
# or https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_syntax
# committed on 18 February 2019 by tibbs ( https://pagure.io/user/tibbs ) in
# https://pagure.io/packaging-committee/c/8d0cec97aedc9b34658d004e3a28123f36404324
# Hence I have the impression, that only the main section of a spec file is
# interpreted in a shell called with the option `-e', but not the scriptlets
# (`%%pre*`, `%%post*`, `%%trigger*` and `%%file*`).

%changelog
* Thu Sep  9 1999 olf <Olf0@users.noreply.github.com> - 99.99.99
- See %{url}/releases