On Jun 2 23:21, Yaakov S wrote: > I think the best solution is to let cygport detect susceptible apps > and generate .manifest files automatically. > > 1. AFAICS, this affects EXEs with names containing "install", "patch", > "setup", or "update". Are there any more patterns?
I never saw more than exactly this list. > 2. According to MSDN[1], the name attribute of the assemblyIdentity > subelement should be uniquely named in a Organization.Division.Name > format. Our existing manifests don't do that; should we? Does it > matter? I don't know if it matters, but it certainly doesn't hurt either. As a suggestion, when automating this, the name could be constructed like this: Organization=Cygwin Division=<packagename> Name=<executable> Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
