Thorsten, Thanks for volunteering. If you are volunteering to do some QA that would be AWESOME. I think the best way you could help out of that front would be to be available to do bug verification? i.e. we would point you to a bug that we believe has been fixed, you could grab it from Gerrit and verify whether or not it has actually addressed the issue.
As for the SO question, not sure, I suspect we didn't do it mainly because it was more complicated, but I don't understand well enough how Linux manages that stuff to comment further. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thorsten Alteholz Sent: Thursday, May 05, 2016 9:17 AM To: [email protected] Subject: [Allseen-core] Debian packages and QA Hi, as you might remember some time ago Cleto Martin wanted to create official Debian packages from the Alljoyn Framework. Unfortunately he had to drop his plans and so I would like to fill in for him. As I might learn most about the software by doing QA work, is there anything I can do in this field? Anyway, while preparing the Debian package for the Alljoyn core I stumbled upon a question. Is there a reason why you use shared libraries but without soname? I only saw: libs.append(about_env.SharedLibrary('alljoyn_about', shobjs)) but wouldn't be something like libs.append(about_env.SharedLibrary('alljoyn_about', shobjs, SHLIBVERSION='1504')) more general? As long as some parts of the framework don't move to the latest core version, it might make sense to install different versions in parallel, doesn't it? Best regards Thorsten _______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core _______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
