-
Notifications
You must be signed in to change notification settings - Fork 347
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 spec file needed to build rpms #111
base: master
Are you sure you want to change the base?
Changes from 2 commits
acbc2fa
8c19a0a
2c8589b
7d4d971
c1ec745
c55fffb
512f31b
663474f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
Name: dumb-init | ||
Version: 1.1.3 | ||
Release: 2%{?dist} | ||
Summary: Entry-point for containers that proxies signals | ||
|
||
License: MIT | ||
URL: https://github.com/Yelp/dumb-init | ||
Source0: https://github.com/Yelp/dumb-init/archive/v%{version}.tar.gz | ||
|
||
BuildRequires: vim-common | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why does this build-depend on vim-common? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. still curious why this depends on vim-common? (GitHub buried my original comment, it seems) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
because I have a line that runs
You can make it depend on /bin/xxd as filename if you wish |
||
BuildRequires: help2man | ||
|
||
%description | ||
dumb-init is a simple process supervisor and init system designed to run as | ||
PID 1 inside minimal container environments (such as Docker). | ||
|
||
* It can handle orphaned zombie processes. | ||
* It can pass signals properly for simple containers. | ||
|
||
%prep | ||
%setup -q | ||
|
||
%build | ||
|
||
# if we are building a release then this is not needed | ||
# make VERSION.h | ||
gcc -std=gnu99 %{optflags} -o %{name} dumb-init.c | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would it make sense to statically compile here like we do for the Debian packages? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no, fedora has quality guidelines and they require it to be dynamically linked. https://fedoraproject.org/wiki/Packaging:Guidelines#Statically_Linking_Executables I have opened a review ticket |
||
help2man --no-discard-stderr --include debian/help2man --no-info --name '%{summary}' ./%{name} | gzip -9 > %{name}.1.gz | ||
|
||
|
||
%install | ||
rm -rf $RPM_BUILD_ROOT | ||
mkdir -p "${RPM_BUILD_ROOT}/%{_bindir}" "${RPM_BUILD_ROOT}/%{_mandir}/man1/" | ||
cp %{name} "${RPM_BUILD_ROOT}/%{_bindir}/" | ||
cp %{name}.1.gz "${RPM_BUILD_ROOT}/%{_mandir}/man1/" | ||
|
||
%files | ||
%{_bindir}/%{name} | ||
%license LICENSE | ||
%doc README.md | ||
%doc %{_mandir}/man1/%{name}.1.gz | ||
|
||
|
||
%changelog | ||
* Mon Aug 15 2016 alsadi <[email protected]> - 1.1.3-2 | ||
- initial packaging |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please update to current version