BuildRequires - flex and bison

[seth vidal]

On Thu, 2006-05-18 at 16:29 +0200, Ralf Corsepius wrote:
> On Thu, 2006-05-18 at 10:16 -0400, seth vidal wrote:
> > On Thu, 2006-05-18 at 16:10 +0200, Ralf Corsepius wrote:
> > > On Thu, 2006-05-18 at 14:53 +0100, Paul Howarth wrote:
> > > > Kevin Kofler wrote:
> > > > > Ralf Corsepius <rc040203 at ...> writes:
> > > > >> Also, I am not sure if the PackageGuideLines allow packages downloading
> > > > >> documents from external sources. 
> > > > > 
> > > > > Of course they do!
> > > > >>From the "Hey, let's remove Firefox, it 'downloads documents from external 
> > > > > sources'!" dept.,
> > > > 
> > > > Methinks Ralf was referring to build-time downloading, not run-time 
> > > > downloading.
> > > Me was referring to unattended background downloads of data files
> > > (configuration- files, data files, text files).
> > > 
> > > Concerns along the lines "What puts mock into a special position" that
> > > it is allowed to automatically pull *config* files unsupervised from a
> > > remote location:
> > > 
> > > Wrt. this, I don't see how mock is any different from
> > > * applications contacting a remote counter each time they start up.
> > > * games loading their game data from a remote file.
> > > * applications dynamically installing plug ins from remote.
> > > ...
> > > 
> > > Another concern are usability (fedoraproject.org bottlenecking mock),
> > > and security.
> > 
> > That's like saying that yum should ship with all the metadata it will
> > ever need b/c it shouldn't be allowed to download files from the
> > network.
> Yum is *SPECIAL*
> 
> > mock isn't downloading anything special, yum, being used by mock, is.
> mock is an arbitrary application.

mock is an arbitrary application which is specifically calling yum.

yum is downloading the files.

so if yum is special then there's no problem here.

-sv