On 8/31/05, Jim Perrin <[EMAIL PROTECTED]> wrote:
> > RHEL/CentOS are not designed to build in a chroot.
> >
> > Fortunately I build all my packages in a clean chroot for cAos, so I
> > know they work.  You can find build logs, packages, and
> > post-dependency package lists for each package at, e.g.,
> > http://mirror.caosity.org/cAos-2/ext/autobuilder/i386/00_LOGS/mej/eet/
> >
> 
> I've been using skvidal's mock buildroot, and it works just fine for
> the packages I build. I'm not doing a full distro rebuild, just
> packages for e, some updates to rhel, like gaim, newer rdesktop, and
> some apache modules. It works fine, and also lets me see the
> dependency tree in a much clearer fashion.
> 
>  In any event I had some time to sit down and read the link Didier
> posted, and I don't see how it hurts anything to spell out the
> Requires. It might be redundant, but that would be about it. 

Nobody said it would hurt. :) But it's redundant. Most people would
let RPM do the job and find it by itself. If you look at Fedora core
extras specs, you' ll see that the majority would only specify the
BuildRequires unless of course the Requires is not that obvious.

I maintain my repo only by specifying BuildRequires in specs. So far
it has correctly calculated run-time dependencies based on the
build-time dependencies. And nobody has complained about libraries
failing to get into their box.



-- 
With kind regards,
Didier.

------------
Yum/apt repository for DR17/EFL: http://sps.nus.edu.sg/~didierbe

Didier F.B Casse
PhD candidate, Singapore Synchrotron Light Source (SSLS)
National University of Singapore.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to