source: projects/specs/trunk/s/scons/scons-vl.spec @ 9224

Revision 9224, 3.2 KB checked in by Takemikaduchi, 9 years ago (diff)

new upstream release

Line 
1Summary:        An Open Source software construction tool
2Summary(ja):    オープンソースソフトウエア構築ツール
3Name:           scons
4Version:        2.3.4
5Release:        1%{?_dist_release}
6Source:         %{name}-%{version}.tar.gz
7
8Group:          Development/Tools
9License:        MIT
10URL:            http://www.scons.org/
11
12BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
13BuildArch:      noarch
14BuildRequires:  python-devel
15
16%description
17SCons is an Open Source software construction tool--that is, a build
18tool; an improved substitute for the classic Make utility; a better way
19to build software.  SCons is based on the design which won the Software
20Carpentry build tool design competition in August 2000.
21
22SCons "configuration files" are Python scripts, eliminating the need
23to learn a new build tool syntax.  SCons maintains a global view of
24all dependencies in a tree, and can scan source (or other) files for
25implicit dependencies, such as files specified on #include lines.  SCons
26uses MD5 signatures to rebuild only when the contents of a file have
27really changed, not just when the timestamp has been touched.  SCons
28supports side-by-side variant builds, and is easily extended with user-
29defined Builder and/or Scanner objects.
30
31%prep
32%setup -q
33
34%build
35CFLAGS="$RPM_OPT_FLAGS" %{__python} setup.py build
36
37%install
38rm -rf $RPM_BUILD_ROOT
39%{__python} setup.py install \
40  --root=$RPM_BUILD_ROOT --record=INSTALLED_FILES \
41  --install-lib=%{_prefix}/lib/scons --install-scripts=%{_bindir} --install-data=%{_datadir}
42
43mkdir -p $RPM_BUILD_ROOT%{_mandir}/man1
44cp -f scons.1 sconsign.1 $RPM_BUILD_ROOT%{_mandir}/man1
45
46%clean
47rm -rf $RPM_BUILD_ROOT
48
49%files
50%defattr(-,root,root,-)
51%doc CHANGES.txt LICENSE.txt README.txt RELEASE.txt
52%{_bindir}/*
53%{_prefix}/lib/scons
54%{_mandir}/man*/*
55
56%changelog
57* Sat Jan 03 2015 Yoji TOYODA <bsyamato@sea.plala.or.jp> 2.3.4-1
58- new upstream release
59
60* Thu Mar 13 2014 NAKAMURA Kenta <kenta@vinelinux.org> 2.3.1-1
61- new upstream release
62
63* Sun Jun 10 2012 Toshiharu Kudoh <toshi.kd2@gmail.com> 2.1.0-1
64- new upstream release
65
66* Sun Feb 21 2010 Shu KONNO <owa@bg.wakwak.com> 1.2.0-2
67- rebuilt with new toolchain
68
69* Sat Apr 25 2009 Shu KONNO <owa@bg.wakwak.com> 1.2.0-1
70- new upstream release
71
72* Sat Oct 11 2008 Shu KONNO <owa@bg.wakwak.com> 1.1-1
73- new upstream release
74- applied new versioning policy, spec in utf-8
75
76* Fri Jun 08 2007 Daisuke SUZUKI <daisuke@linux.or.jp> 0.97-0vl1
77- new upstream release
78
79* Sat Oct 22 2005 Daisuke SUZUKI <daisuke@linux.or.jp> 0.96-0vl1
80- initial build for Vine Linux
81
82* Fri Apr  7 2005 Michael Schwendt <mschwendt[AT]users.sf.net>
83- rebuilt
84
85* Tue Jan 25 2005 Thorsten Leemhuis <fedora[AT]leemhuis[DOT]info> 0.96-4
86- Place libs in {_prefix}/lib/ and not in {libdir}; fixes x86_64 problems
87- Adjust minor bits to be in sync with python-spec-template
88
89* Wed Nov 10 2004 Matthias Saou <http://freshrpms.net/> 0.96-3
90- Bump release to provide Extras upgrade path.
91
92* Thu Aug 19 2004 Gerard Milmeister <gemi@bluewin.ch> - 0:0.96-0.fdr.1
93- New Version 0.96
94
95* Thu Apr 15 2004 Gerard Milmeister <gemi@bluewin.ch> - 0:0.95-0.fdr.1
96- New Version 0.95
97
98* Fri Nov  7 2003 Gerard Milmeister <gemi@bluewin.ch> - 0:0.93-0.fdr.1
99- First Fedora release
100
101
Note: See TracBrowser for help on using the repository browser.