Hello fellow developers,
On Sun, Apr 13, 2025 at 05:25:59PM +0200, Helmut Grohne wrote:
> All of the perl ones have been filed and gregor already fixed (thanks!)
> a significant fraction including all 11 perl-xs-dev ones. I
> guess that on third of these is fixed in git or unstable.
I guess half
Hello fellow developers,
On Thu, Apr 10, 2025 at 07:37:32AM +0200, Helmut Grohne wrote:
> how about libc6-dev stops depending on libcrypt-dev?
with minor disagreement in details, I have received much positive
feedback and therefore moved forward.
> So far so good. That's 1 + 95 + 11 + 1 = 108 so
Hi,
On 2025-04-10 07:37, Helmut Grohne wrote:
> Hello fellow developers,
[ Snip ]
> Question 1: Do you see important aspects missed in this analysis?
No
> Question 2: Do you agree that this change is worth the effort?
I don't know. I do not see a huge benefit from the glibc point of view,
bu
Hi Marco,
On Thu, Apr 10, 2025 at 11:01:24AM +0200, Marco d'Itri wrote:
> On Apr 10, Helmut Grohne wrote:
> > how about libc6-dev stops depending on libcrypt-dev?
> Sure.
Thanks for the feedback.
> > material of course. Also libc6-dev would still "Recommends:
> > libcrypt-dev", but libcrypt-de
On Apr 10, Helmut Grohne wrote:
how about libc6-dev stops depending on libcrypt-dev?
Sure.
material of course. Also libc6-dev would still "Recommends:
libcrypt-dev", but libcrypt-dev would no longer be build-essential.
What purpose would this Recommends solve?
Assuming "no" and "yes" as a
5 matches
Mail list logo
