Jonas Meurer wrote: > and even if the API doesn't change with every release, at least the ABI > does. libcryptsetup neither seems to have a soname nor a symbols file, > so maintaining ABI compability and all the stuff seems to be a lot of > work. The libcryptsetup API has no chance for a stable ABI atm. The struct crypt_options is exported in the header and applications need to fill in the fields. So any change in crypt_options, like adding new fields, breaks the ABI. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
