Extras build system back up
by Dan Williams
Hi,
We're back up and using the latest plague code. yum update your
plague-client and you should be good to go.
Dan
16 years, 11 months
- 3
- 7
example of buildsys rpm
by Clark Williams
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
All,
I hand-hacked this specfile together using the FC4 buildroots.xml as
the starting point. Just wanted to put together a test to see how
complicated it would be (it wasn't; witness the fact that I did it :).
I've got a start on a small python script that will parse the current
buildroots and generate spec files for the various configurations.
I built it like this:
rpmbuild --define "_sourcedir $(PWD)" --define "_builddir
$(PWD)/buildsys" --define "_srcrpmdir $(PWD)/buildsys" --define
"_rpmdir $(PWD)/buildsys" -ba buildsys-minimal.spec
It generates a small binary RPM (and an SRPM) that contains one file,
buildsys-minimal.spec and requires all the listed packages. I
originally had BuildRequires and then changed to Requires, just
because it's easy to query the resulting binary RPM for requires. I
suspect to be totally correct we would need to go back to BuildRequires.
Anyway, that's what I thought Seth was talking about with his RPM
idea. What do you think?
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEMsh0Hyuj/+TTEp0RAqLxAKDeNQr71ObH68KB/8cUeDC/IwnTBACdEZWP
zCVlr03vYsHKh5VBNzOwN7Q=
=sdkS
-----END PGP SIGNATURE-----
Summary: Dependency package for minimal buildroot
Name: buildsys-minimal
Version: fc5
Release: 1
License: GPL
Group: Development/Build Tools
Source0: buildsys-minimal.spec
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
Requires: bash
Requires: glibc
Requires: python
Requires: createrepo
Requires: rpm
Requires: rpm-python
Requires: initscripts
Requires: chkconfig
Requires: fedora-release
#Requires: buildsys-macros
Requires: coreutils
Requires: findutils
Requires: openssh-server
Requires: which
Requires: udev
Requires: rpm-build
Requires: make
Requires: gcc
Requires: tar
Requires: gzip
Requires: patch
Requires: unzip
Requires: bzip2
Requires: diffutils
Requires: cpio
Requires: elfutils
Requires: intltool
Requires: redhat-rpm-config
Requires: gcc-c++
Requires: autoconf
Requires: gettext
Requires: automake
Requires: gdb
Requires: flex
Requires: libtool
Requires: strace
Requires: bison
Requires: binutils
Requires: patchutils
Requires: byacc
Requires: diffstat
Requires: perl-XML-Parser
Requires: perl-XML-Dumper
Requires: perl-XML-SAX
Requires: ctags
Requires: automake14
Requires: automake15
Requires: automake16
Requires: automake17
Requires: doxygen
Requires: indent
Requires: pkgconfig
%description
%prep
rm -rf %{buildroot}
mkdir -p %{buildroot}/var/lib/mock
cp %{SOURCE0} %{buildroot}/var/lib/mock
%build
%install
%clean
%files
%defattr(-,root,root,-)
%doc
/var/lib/mock/buildsys-minimal.spec
%changelog
* Tue Apr 4 2006 Clark Williams <williams(a)redhat.com> - 1.0-1
- Initial build.
17 years, 5 months
- 9
- 23
mock buildroot definitions
by seth vidal
Hey,
So it was brought up a while ago that due to the changing nature of the
comps.xml format that we should not rely on it for the buildroot
installations in mock. The idea a while back was to just have a
'buildroot' rpm that required all the stuff that would normally be in
the comps.xml group. Then we could just install that rpm and it pulls in
the rest of the buildroot components.
What do folks think? Worth going through the process to do it?
-sv
17 years, 5 months
- 11
- 18
- ← Newer
- 1
- Older →