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

alac.spec #2

Open
noohgnas opened this issue Mar 6, 2017 · 2 comments
Open

alac.spec #2

noohgnas opened this issue Mar 6, 2017 · 2 comments

Comments

@noohgnas
Copy link

noohgnas commented Mar 6, 2017

Hi Mike,
How about add alac.spec file in your repository like following. I just modify a little bit from your shairpot-sync.spec file.

Name:           alac
Version:        0.0.7
Release:        1
Summary:        A clone of the Apple Lossless Audio Codec.

Group:          Applications/Multimedia
License:        GPL
URL:            https://github.com/mikebrady/alac
Source0:        https://github.com/mikebrady/%{name}/archive/%{version}.tar.gz#/%{name}-%{version}.tar.gz

BuildRequires:  autoconf
BuildRequires:  automake
BuildRequires:  libconfig-devel

%description
This is a clone of the Apple Lossless Audio Codec (ALAC) repository at http://alac.macosforge.org with added files to enable it to be built using GNU autotools. Use it to build and install the ALAC library libalac.

%prep
%setup -q

%build
autoreconf -i -f
%configure
make %{?_smp_mflags}

%install
make install DESTDIR=%{buildroot}


%files
%doc AUTHORS LICENSE README.md
%attr(0644, root, root) "/usr/include/alac/"
%attr(0644, root, root) "/usr/lib64/libalac*"
%attr(0644, root, root) "/usr/lib64/pkgconfig/alac.pc"


%changelog
* Mon Mar 6 2017 Sanghoon LEE <[email protected]> 0.0.7-1
- Initial spec file
@mikebrady
Copy link
Owner

Sorry to have overlooked this for so long. I'll add it, but the license stuff isn't really right. In fact, there are two licenses, an Apple one and an Apache one. Any idea what to put in the License: line?

@noohgnas
Copy link
Author

@mikebrady I'm sorry that I didn't have knowledge of open source license. However, according to RPM licensing guides said dual license is possible I think. https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#Dual_Licensing_Scenarios

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

No branches or pull requests

2 participants