-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create SRPMs / support build systems #36
Comments
* Update sfos-upgrade.spec * fixes #36 (#37) * fixes #36 - c.f https://fedoraproject.org/wiki/Packaging:SourceURL#Git_Tags - builds fine on my local system - source URL tested with curl -O -L - not yet tried on OBS, in a train at the moment * Update sfos-upgrade.spec
A canonical web-link to the release TARballs (tar.gz archives of released versions) can be constructed by setting adequate names for the git-tags to be used as hinted in the Fedora RPM wiki and pointed out by @pcfe in PR #37. |
See the first try to adapt to obs with subsequent discussion and a separate discussion, the first one spawned / experimental commit a31be78.
SRPM is now provided, see this comment for details.
But I still don't know / understand, if this (an SRPM) resolves the original issue (integration into build systems, e.g. obs).
P.S.: Building SRPMs works now, per commit 41d29a4.
An SRPM can be downloaded e.g. per
curl -sSLO https://github.com/Olf0/%{name}/releases/download/%{version}-%{release}/%{name}-%{version}-%{release}.src.rpm
, while the original TAR.GZ source archive can be downloaded e.g. percurl -sSLo %{name}-%{version}-%{release}.tar.gz https://github.com/Olf0/%{name}/archive/%{version}-%{release}.tar.gz
(that is equivalent tocurl -sSLo %{source} %{source1}
, when SOURCE1 was still set, i.e. before aforementioned commit 41d29a4).The text was updated successfully, but these errors were encountered: