Helmut Grohne dixit: >be dropping those dependencies. If you do that in a profile, the >contents of the mksh package vary with the profile. However, if you
The contents vary anyway. If a libc is not available (ok, this does not happen with normal Debian Build-Depends) or produces a faulty executable, it’s skipped. (And yes, this is by design.) >split mksh-static to a separate package, you only change the package mksh-static is just a symlink to the “best” one, but I ship all ones. >point, I'm aiming for three categories: Low hanging fruit, tooling bugs >and packages must be cross buildable for some reason. The bug at hand OK, works for me. >That may be correct, but I still fail to see why I would want a compact Yes, which is why I’m not going there, it’s off-topic, I have reasons and not the nerve to explain to someone who fails to see it. There are other factors in play as well. >I still wonder what do do about the bug now. We've figured that no, Nothing. >So how bad would it be to close this bug with the wontfix tag? Or leave it open with it. I don’t care. bye, //mirabilos -- 22:20⎜<asarch> The crazy that persists in his craziness becomes a master 22:21⎜<asarch> And the distance between the craziness and geniality is only measured by the success 18:35⎜<asarch> "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
