Re: unexpected package dependency

2016-02-22 Thread Lowell Gilbert
Andriy Gapon writes: > On 19/02/2016 03:55, Perry Hutchison wrote: >> Andriy Gapon wrote: >>> On 17/02/2016 11:28, Perry Hutchison wrote: I had not expected to find gcc listed (in packagesite.yaml) as a dependency of the sysutils/cpuburn package. I

Re: unexpected package dependency

2016-02-22 Thread Andriy Gapon
On 19/02/2016 03:55, Perry Hutchison wrote: > Andriy Gapon wrote: >> On 17/02/2016 11:28, Perry Hutchison wrote: >>> I had not expected to find gcc listed (in packagesite.yaml) as a >>> dependency of the sysutils/cpuburn package. I can understand a >>> _port_ needing gcc (at

Re: unexpected package dependency

2016-02-18 Thread Perry Hutchison
Andriy Gapon wrote: > On 17/02/2016 11:28, Perry Hutchison wrote: > > I had not expected to find gcc listed (in packagesite.yaml) as a > > dependency of the sysutils/cpuburn package. I can understand a > > _port_ needing gcc (at build time), but does the cpuburn _package_ > >

Re: unexpected package dependency

2016-02-17 Thread Andriy Gapon
On 17/02/2016 11:28, Perry Hutchison wrote: > I had not expected to find gcc listed (in packagesite.yaml) as a > dependency of the sysutils/cpuburn package. I can understand a > _port_ needing gcc (at build time), but does the cpuburn _package_ > actually require gcc at _runtime_? > I don't

unexpected package dependency

2016-02-17 Thread Perry Hutchison
I had not expected to find gcc listed (in packagesite.yaml) as a dependency of the sysutils/cpuburn package. I can understand a _port_ needing gcc (at build time), but does the cpuburn _package_ actually require gcc at _runtime_? ___