[ Adding LSARC-ext and desktop-discuss aliases. ]
John (Fischer) and Darren (Moffat) - questions from Brian for you below. I will hold off on creating a new contract for OpenSSL<->Lynx until this is resolved. - Dermot On 11/12/08 22:38, Brian Cameron wrote: > > John: > >> It sounds like the JDS build is broken. I can not >> imagine mahjongg needing OpenSSL. > > The fact that libgnomevfs-2.so uses openssl makes any program > which uses gnomevfs seem to link against OpenSSL. Sorry for the > confusion. > > I will detail which programs specifically use OpenSSL in the desktop > stack below: > > The following five programs in the desktop stack use OpenSSL and > already have contracts: > > - /usr/bin/gkrellm (contract #25) > - /usr/bin/irssi (contract #25) > - /usr/bin/rdesktop (contract #16) > - /usr/bin/transmission (contract #25) > - /usr/lib/libgnomevfs-2.so (contract #7) > > The following three programs in the desktop stack use OpenSSL and > do not seem to have contracts. All three would be jds/gnome/applications: > > - /usr/bin/lynx > - /usr/bin/w3m > - /usr/bin/xchat > > The following three programs are going to need contracts once > PyOpenSSL integrates, which is going to be very soon. elisa and > codeina would be jds/gnome/applications and Python-Twisted is > jds/gnome/libraries > > - Python-Twisted > - elisa > - codeina > > So, do you want us to create 6 new contracts, or should we just create > a single contract for the 6 new programs, or should we otherwise reorganize > our Desktop <-> OpenSSL contracts so they are easier to manage? Perhaps > it would be a good idea to get rid of the 3 existing contracts and replace > them with one contract that covers all desktop consolidation usages? > > Darren, let me know what you think is most appropriate, and we'll put > together the contracts so we can get this in order. > > Thanks, > > Brian >
