%global commitdate 2026-01-01
%global commit f3731e5d9e15726f6d8aba2d2ee2dc2f13d7e4a5
%global shortcommit %(c=%{commit}; echo ${c:0:7})


Name:       witr
Version:    0.1.5
Release:    1%{?dist}
Summary:    Why is this running
License:    Apache-2.0
URL:        https://github.com/pranshuparmar/witr
Source0:    %{url}/archive/v%{version}/%{name}-%{version}.tar.gz

BuildRequires: golang >= 1.25.5
BuildRequires: coreutils

%description
witr exists to answer a single question:
    Why is this running?
When something is running on a system — whether it is a process, a service, 
or something bound to a port — there is always a cause. That cause is often 
indirect, non-obvious, or spread across multiple layers such as supervisors, 
containers, services, or shells.

Existing tools (ps, top, lsof, ss, systemctl, docker ps) expose state and 
metadata. They show what is running, but leave the user to infer why by 
manually correlating outputs across tools.

witr makes that causality explicit.

It explains where a running thing came from, how it was started, and what 
chain of systems is responsible for it existing right now, in a single, 
human-readable output.

%prep
%autosetup -p1

%build
go build \
    -ldflags "-X main.version=%{version} -X main.commit=%{shortcommit} -X main.buildDate=%{commitdate}" \
    -o _build/%{name} ./cmd/witr

%install
install -Dpm 0755 _build/%{name} %{buildroot}%{_bindir}/%{name}
mkdir -p %{buildroot}/%{_mandir}/man1/
install -Dpm 0644 docs/%{name}.1 %{buildroot}/%{_mandir}/man1/%{name}.1


%files
%license LICENSE
%doc README.md 
%{_bindir}/%{name}
%{_mandir}/man1/*.1*

%changelog
* Fri Jan 02 2026 josef radinger <cheese@nosuchhost.net> - 0.1.5-1
- bump version
- reformat description

* Tue Dec 30 2025 josef radinger <cheese@nosuchhost.net> - 0.1.3-1
- bump version

* Sun Dec 28 2025 josef radinger <cheese@nosuchhost.net> - 0.1.1-1
- fix builddate
- bump version

* Sat Dec 27 2025 josef radinger <cheese@nosuchhost.net> - 0.1.0-1
- Initial package