We need to be able to make changes to the framework and build rpms for them
to give to other developers. Without the functionality to build rpms there
it hurts any value that we get from upgrading versions in the first place
because we would need to implement rpm building ourselves.
On Thu, Mar 19, 2020 at 11:12 AM James Kulp jek@parera.com wrote:
On 3/19/20 11:02 AM, Chris Hinkey wrote:
I am looking at upgrading my project to use a newer version of OpenCPI(on
1.5) currently. The broken-ness of rpm building in 1.6 is a roadblock
for
this is rpm functionality still expecting to return in 1.7 ?
We need to be able to make changes to the framework and build rpms for them
to give to other developers. Without the functionality to build rpms there
it hurts any value that we get from upgrading versions in the first place
because we would need to implement rpm building ourselves.
On Thu, Mar 19, 2020 at 11:12 AM James Kulp <jek@parera.com> wrote:
> On 3/19/20 11:02 AM, Chris Hinkey wrote:
> > I am looking at upgrading my project to use a newer version of OpenCPI(on
> > 1.5) currently. The broken-ness of rpm building in 1.6 is a roadblock
> for
> > this is rpm functionality still expecting to return in 1.7 ?
> >
