On 18/06/2023 09:45, Abou Al Montacir wrote:
However, fpc units are kind of statically linked libraries. And in
this case, one ma want a rebuild of all reverse dependencies in order
to ensure a bug fix is propagated on all binaries.
Example: Suppose we discover a vulnerability in a unit. We
Hi,
On 17-06-2023 19:47, Abou Al Montacir wrote:
So maybe the solution would be to make the units dependency strict. I
meant id fp-units-foo build depends on fp-unit-bar then it should depend
on it strictly. And any rebuild of fp-units-bar shall trigger rebuild of
fp-units-foo.
This sounds
Hi Paul,
On Mon, 2023-02-20 at 20:57 +0100, Paul Gevers wrote:
> The Release Team scripts don't care about the section, they look at
> installability. But if we compare the units to C libraries, we normally
> asks library maintainers to *not* version the dev packages, because then
> all
Hi Abou,
On 18-02-2023 12:17, Abou Al Montacir wrote:
On Thu, 2021-12-30 at 22:30 +0100, Abou Al Montacir wrote:
Maybe we should move
the fp-units-$bar packages to the library section too and embed the ABI
version into the package name.
I like that idea. Let's go that way.
...
I don't
Hi Paul,
I went again though this ticket and changed a bit my mind
On Thu, 2021-12-30 at 22:30 +0100, Abou Al Montacir wrote:
> > Maybe we should move
> > the fp-units-$bar packages to the library section too and embed the ABI
> > version into the package name.
>
>
> I like that idea. Let's
5 matches
Mail list logo
