Re: Movement of FAQ's
От | Dave Page |
---|---|
Тема | Re: Movement of FAQ's |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4306AC7@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Movement of FAQ's (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Movement of FAQ's
Re: Movement of FAQ's |
Список | pgsql-www |
> -----Original Message----- > From: Bruce Momjian [mailto:pgman@candle.pha.pa.us] > Sent: 11 October 2004 16:03 > To: Dave Page > Cc: PostgreSQL www > Subject: Re: [pgsql-www] Movement of FAQ's > > Dave Page wrote: > > > Oh, no I didn't. Would you like to make adjustments to it and/or > > > FAQ_MINGW so they point to each other and don't duplicate > > > information? > > > > I'm not entirely convinced that's the right answer. The > main concern > > is making things easy for the users - that's what I've tried to do > > with the installer faq (which I now notice Magnus has been > editting!) > > by covering both installer specific stuff, and > non-installer specific; > > a kindof 1 stop shop for all Win32 faqs. I appreciate that we don't > > necessarily want the installer stuff in the main tree however. What > > about making the version in the tree a subset of our one, simply > > covering the mingw/compiliation issues which I can include in one > > standalone section in our faq? > > Both FAQ's are going to change over time, I am sure. I see > no problem in giving them a web link to the FAQ_MINGW for > compilation issues. > Having the Mingw outside our CVS doesn't make sense to me. No, and I don't think it should be outside. What I would like to avoid if possible though, is having win32 problems split across different FAQs. Most end users won't care about whether something is a Mingw or Installer issue and will just get frustrated if they cannot find the info they need. I guess the best answer might be to clearly mark the Mingw FAQ as a diy-compilation FAQ, and include a link for 'normal' end users to the installer FAQ in which we try to include all relevant q&a's. Regards, Dave.
В списке pgsql-www по дате отправления: