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 Thu, 10 Apr 2025 07:37:32 +0200, Helmut Grohne wrote:
I sorted those logs and
you may now find them at
https://people.debian.org/~helmutg/glibc-no-crypt/logs/.
Thanks.
Beyond that, 11
packages build a perl extension module for testing purposes and
therefore need "Build-Depends: perl-xs-de
[ Thanks for this. Awesome work! ]
El 10/4/25 a las 11:43, Helmut Grohne escribió:
My thinking here was to reduce the annoyance for users by degrading the
dependency softly. I was told that some users expect to be able to build
perl extensions without installing libperl-dev (which is why libperl
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
On Thu, 10 Apr 2025 at 07:37:32 +0200, Helmut Grohne wrote:
how about libc6-dev stops depending on libcrypt-dev?
I think this is a good idea for early in the forky cycle.
I also investigated
all apt-cache rdepends libcrypt1. That results in 151 source packages.
...
* steam-installer
This
Hello fellow developers,
how about libc6-dev stops depending on libcrypt-dev?
I mean for real. We cannot do it right away. The proposal is forky
material of course. Also libc6-dev would still "Recommends:
libcrypt-dev", but libcrypt-dev would no longer be build-essential.
The obvious "why" que
8 matches
Mail list logo
