Ainsi parlait Stefan van der Eijk :
> >> I'm using a dedicated machine (in a VMware) to do this at the moment.
> >> A normal user performs the rebuilding, so damage to the system should
> >> be limited.
> >>
> >> When Jeff Garzik was still employed at Mandrakesoft we discussed using
> >> a chroot() environment to build packages. The idea was to install a
> >> stripped system (basesystem + rpm-build + BuildRequires) for every
> >> package to be rebuilt in a chroot environment. In the end we didn't go
> >> through with the idea.
> >
> > Creating a slim clean build environment for each package seems to be
> > overkill (to me). I simply don't have the resources. I have one fat
> > clean build environment for each distribution.
>
> Let me rephraise that. The script will create a build environment, build
> the package, remove the build environment, and restarts. Keeping the build
> environment intact after rebuilding for each package is insane.
>
> > Building as a user helps you not to pollute your build environment, but
> > for each violation the build is halted. Compare this to rpmbuild telling
> > you only the first file from %files it cannot find ;)
>
> Yes. My scripts (mentioned in a earlier post --> can be found at:
> http://eijk.homelinux.org/~stefan/slbd.html) do this. After each build a
> cleanup is done (temp & build directories are emptied, BuildRequires are
> de-installed).
>
> Need to setup a SF project for the scripts...
May i suggest joining youri project instead (see http://youri.zarb.org), and
make automatic and safe package building one of the objectives of the project
?
I've been in touch with Matthias, the guy maintaining freshrpm.net, at FOSDEM,
he would be very interested by such topic. He already started such project
two years ago on sf.net, without interesting anyone else as him.
--
All components become obsolete.
-- Murphy's Computer Laws n�8
