Björn Persson wrote:
> Kevin Fenzi wrote:
> > So, ideally here, there's a new gcc upgrade, the gcc maintainer
> > would build with a compat-libgnat subpackage that installs libgnat
> > in another place. Then they build the new gcc without it. You then
> > can buildrequire that compat-libgnat so yo
Dan Horák wrote:
> On Mon, 7 Dec 2015 11:32:44 +0100
> Björn Persson wrote:
>
> > Kevin Fenzi wrote:
> > > On Tue, 1 Dec 2015 15:46:26 +0100
> > > Björn Persson wrote:
> > > > GPRbuild is
> > > > linked to XMLada, and both GPRbuild and XMLada are linked to
> > > > libgnat, as are all other Ada
On Mon, 7 Dec 2015 11:32:44 +0100
Björn Persson wrote:
> Kevin Fenzi wrote:
> > On Tue, 1 Dec 2015 15:46:26 +0100
> > Björn Persson wrote:
> > > GPRbuild is
> > > linked to XMLada, and both GPRbuild and XMLada are linked to
> > > libgnat, as are all other Ada programs and libraries.
> > >
> > >
Kevin Fenzi wrote:
> On Tue, 1 Dec 2015 15:46:26 +0100
> Björn Persson wrote:
> > GPRbuild is
> > linked to XMLada, and both GPRbuild and XMLada are linked to libgnat,
> > as are all other Ada programs and libraries.
> >
> > With every major GCC upgrade the soname of libgnat changes, and all
> >
On Tue, 1 Dec 2015 15:46:26 +0100
Björn Persson wrote:
> So the L source package shall temporarily contain two versions of the
> source tarball and build them both, and then install one as usual and
> extract only the binary library from the other? That would complicate
> the spec quite a bit eve
Kevin Fenzi wrote:
> On Sun, 29 Nov 2015 00:35:37 +0100
> Björn Persson wrote:
>
> > Is there a way to deal with the following situation in Koji?
> >
> > · Build tool B has a build-time dependency on itself.
> > · B is linked to library L version 1.
> > · L gets upgraded to version 2, which chan
On Sun, 29 Nov 2015 00:35:37 +0100
Björn Persson wrote:
> Is there a way to deal with the following situation in Koji?
>
> · Build tool B has a build-time dependency on itself.
> · B is linked to library L version 1.
> · L gets upgraded to version 2, which changes its soname.
>
> B needs to be
Is there a way to deal with the following situation in Koji?
· Build tool B has a build-time dependency on itself.
· B is linked to library L version 1.
· L gets upgraded to version 2, which changes its soname.
B needs to be rebuilt to link to libL.so.2, but building B requires a
working B, which
