On Tue, 2011-03-01 at 23:08 +0800, [email protected] wrote: > Package: monodoc-browser > Version: 2.6.2-3 > > Can't these be compiled at the developer's end, and have them sent ready > made, instead of having each users machine crank for many minutes, > spewing out tons of errors? > > > .SqlTypes.SqlChars.Conversion, with xpath: > /Type/Members/Member[@MemberName='op_Conversion']/Docs > Problem: O:System.Data.SqlTypes.SqlDateTime.Conversion, with xpath: > /Type/Members/Member[@MemberName='op_Conversion']/Docs > Problem: O:System.Data.SqlTypes.SqlDateTime.Conversion, with xpath: > /Type/Members/Member[@MemberName='op_Conversion']/Docs > Problem: O:System.Data.SqlTypes.SqlDecimal.Conversion, with xpath: > /Type/Members/Member[@MemberName='op_Conversion']/Docs > > > All I know is I did aptitude install python-gdata monodoc-gdata-manual > on sid.
Short version: not easily. The search index covers all installed document trees - that's sorta the point. As such, we can't just generate a search index at compile time, as the index depends upon the document packages a user has installed. And the doc browser is useless without the index having been generated, so simply not doing it isn't much of an option. I had one idea recently for an alternative approach, but it would be unpleasant for multi-user systems. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
