aboutsummaryrefslogtreecommitdiffstats
path: root/chapter01
diff options
context:
space:
mode:
authorXi Ruoyao <xry111@xry111.site>2023-07-27 09:43:35 +0800
committerXi Ruoyao <xry111@xry111.site>2023-07-27 09:43:57 +0800
commitb15bebf96f9df4260904cb682c1692bcc43891c2 (patch)
tree0e9714cd9fe59aee158d0ab6d2f471142d94719e /chapter01
parentfb3b88e8f288563f26096ecf5eb6d2ad749ae5e5 (diff)
askforhelp: Add a note to stop people from spamming upstream
I've seen two cases of invalid upstream "bug" reports this month because the user has (mis)built LFS. Let's stop this before irritating the upstream maintainers.
Diffstat (limited to 'chapter01')
-rw-r--r--chapter01/askforhelp.xml21
1 files changed, 21 insertions, 0 deletions
diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml
index 367e880c0..405b40804 100644
--- a/chapter01/askforhelp.xml
+++ b/chapter01/askforhelp.xml
@@ -10,6 +10,27 @@
<title>Help</title>
+ <note>
+ <para>
+ We strongly discourage posting your issues building one LFS package
+ directly onto the upstream support channel, without discussing via
+ a LFS support channel listed in <xref linkend="ch-intro-resources"/>
+ first. Doing so is often quite inefficient because the upstream
+ maintainers are rarely familiar with LFS building procedure. Even if
+ you've really hit an upstream issue, the LFS community can still help
+ to isolate the information wanted by the upstream maintainers and make
+ a proper report.
+ </para>
+
+ <para>
+ If you must ask a question directly via an upstream support channel,
+ you shall at least note that many upstream projects have the support
+ channels separated from the bug tracker. The <quote>bug</quote>
+ reports for asking questions are considered invalid and may annoy
+ upstream developers for these projects.
+ </para>
+ </note>
+
<para>If an issue or a question is encountered while working through
this book, please check the FAQ page at <ulink url="&faq-root;#generalfaq"/>.
Questions are often already answered there. If your question is not