Kai Engert (kaie@xxxxxxx) said: > On Wed, 2013-01-23 at 16:31 -0500, Bill Nottingham wrote: > > Essentially, how will we know whether apps work transparently with the > > library changes, and/or if there are apps that are hardcoding old > > locations/methods somewhere? > > we're not yet ready to shake hands, we're starting and giving you the > little finger. Hey, the little finger is certainly better than other fingers. > Today we have a world that seems unorganized, where multiple crypto > toolkits each do their own separate thing. Because some toolkits haven't > offered a complete solution, some applications have used their own > solutions on top of them. > > We cannot solve all of that at once. We must start with a first step. > This first step is to create a common infrastructure. Once that common > infrastructure is ready, then applications can start to use it. > > After that initial step has been completed, we can advertise it and > recommend that new applications use it. And we can start investigating > existing applications and work with maintainers to get them changed to > the use new shared infrastructure. > > The goal for this initial round is to have the shared infrastructure > ready, and to offer a default functionality that applications are able > to use. Nod, I understand - I'm just paranoid about apps doing stupid things on their own that might break. History of changes that are written that say "well written apps should not have any issues" that are immediately followed by us discovering just how many apps aren't well-written. I guess the answer (as usual) is just documentation, documentation, documentation. Bill -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
