Hi Christoph, On Mon, 27 Jan 2020 at 07:23:02 +0100, Christoph Biedl wrote: > As far as I understand however, while such a situation _can_ happen, it > is not very likely.
FWIW our last heavy refactoring was in spring/summer 2018. We obviously won't change the internal interface just “for fun”, but I'm not making the promise it won't change again without prior notice :-P (In the past I've tried to use sources.debian.org and chase uses of our internal interfaces, cf. #904899 for instance, but that's quite tedious and I'm unsure I'll do the same next time.) > So my suggestions, in decreasing order of preference: > > * Creating/using an API for the initramfs code, something you suggested in > another message. Honestly, I haven't checked the code yet whether this > is feasablle. In case cryptsetup-initramfs' current interface is not expressive enough I'm open to extend it. What I object to though, is to be “forced” to freeze & publish our internal interface because some projects blindly started relying on it. > For the moment I'll mostly likely do an upload to experimental. Ack, and just to be clear I won't stand in the way here, only trying to warn you about possible RC bugs further down the road :-P (And bugs that might be difficult to fix gracefully in case the fix requires updating /etc/crypttab.) > I've been waiting for this feature for a long time, therefore I'd like > to collect first experiences with it soon. We should have a sound > solution before the freeze which is still several months away.¹ > […] > ¹ But keep in mind dates in calendars are closer than they appear. Hehe :-) Cheers, -- Guilhem.
signature.asc
Description: PGP signature
