On Ter, 2014-05-13 at 15:03 -0500, Richard Shaw wrote:
> On Tue, May 13, 2014 at 11:23 AM, Ville Skyttä
> wrote:
> On Tue, May 13, 2014 at 5:14 PM, Richard Shaw
> wrote:
> > I would think you would need to step through the BR:'s get
> the capabilities
> >
I've always thought it would be super great to make a distinction of
BuildRequires, and things required to perform build tests... say
TestRequires.
Stepping through the BRs is probably not enough, tests could also be
disabled through this process.
Say for example perl or python scripts are used to
On Tue, 13 May 2014 19:23:50 +0300, Ville Skyttä wrote:
> On Tue, May 13, 2014 at 5:14 PM, Richard Shaw wrote:
> > I would think you would need to step through the BR:'s get the capabilities
> > of the packages that the -devel package pull in, and then check that against
> > the requires of the re
On Tue, May 13, 2014 at 09:14:14AM -0500, Richard Shaw wrote:
> As packages age sometimes build requirements chance and may not be caught
> by the package maintainer. Is there a known way of determining if there are
> unnecessary build requirements in a package?
Yes, using auto-buildrequires:
htt
On Tue, May 13, 2014 at 11:23 AM, Ville Skyttä wrote:
> On Tue, May 13, 2014 at 5:14 PM, Richard Shaw
> wrote:
> > I would think you would need to step through the BR:'s get the
> capabilities
> > of the packages that the -devel package pull in, and then check that
> against
> > the requires of
Am 13.05.2014 18:23, schrieb Ville Skyttä:
> On Tue, May 13, 2014 at 5:14 PM, Richard Shaw wrote:
>> I would think you would need to step through the BR:'s get the capabilities
>> of the packages that the -devel package pull in, and then check that against
>> the requires of the resultant packag
On Tue, May 13, 2014 at 5:14 PM, Richard Shaw wrote:
> I would think you would need to step through the BR:'s get the capabilities
> of the packages that the -devel package pull in, and then check that against
> the requires of the resultant packages.
BR's don't always map/result into any depende
