Skip to content
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

Add RPM spec file #2

Merged
merged 1 commit into from Sep 19, 2015
Merged

Add RPM spec file #2

merged 1 commit into from Sep 19, 2015

Conversation

neingeist
Copy link
Contributor

No description provided.

@@ -0,0 +1,42 @@
Name: catimg
Version: 2.0
Release: 1%{?dist}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this for ?
I found it at https://fedoraproject.org/wiki/Packaging:DistTag

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. On my system (Fedora 22) this adds .fc22 to the version like this:

catimg-2.0-1.fc22

@posva
Copy link
Owner

posva commented Sep 18, 2015

Hey, thanks for the rpm. I've never created one.

I cannot test ATM and I cannot find a validator for these specs. Do you have any clue so I can search a bit more?

@posva
Copy link
Owner

posva commented Sep 18, 2015

I'll add the license and merge this PR tomorrow
Thanks! 😄

@neingeist
Copy link
Contributor Author

Best way to get into spec files: Build a RPM :) On F22:

dnf install rpm-build rpmdevtools
spectool -g catimg.spec # Downloads catimg-2.0.tar.gz
mkdir -p ~/rpmbuild/SOURCES ~/rpmbuild/RPMS/x86_64 ~/rpmbuild/SRPMS
mv catimg-2.0.tar.gz ~/rpmbuild/SOURCES
rpmbuild -ba catimg.spec
# RPM should now be in ~/rpmbuild/RPMS/x86_64

I haven't run any validation/lint tool on the RPM/spec yet.

@neingeist
Copy link
Contributor Author

The Fedora Wiki on creating RPM files:
https://fedoraproject.org/wiki/How_to_create_an_RPM_package

posva added a commit that referenced this pull request Sep 19, 2015
@posva posva merged commit 45ca448 into posva:master Sep 19, 2015
@posva
Copy link
Owner

posva commented Sep 19, 2015

I'll have to update the version field each time I release a new version, don't I?

@neingeist
Copy link
Contributor Author

Yes, it will always build the version specified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants