Tue Apr 13 11:01:17 2021 UTC ()
doc: GNOME and freedesktop.org GitLab links

GNOME and freedesktop.org no longer use Bugzilla for issue tracking.
Both projects switched to Git and GitLab for development.


(cirnatdan)
diff -r1.11 -r1.12 pkgsrc/doc/guide/files/gnome.xml
cvs diff -r1.11 -r1.12 pkgsrc/doc/guide/files/gnome.xml (expand / switch to unified diff)

--- pkgsrc/doc/guide/files/gnome.xml 2020/02/24 21:13:56 1.11
+++ pkgsrc/doc/guide/files/gnome.xml 2021/04/13 11:01:17 1.12
@@ -1,14 +1,14 @@ @@ -1,14 +1,14 @@
1<!-- $NetBSD: gnome.xml,v 1.11 2020/02/24 21:13:56 rillig Exp $ --> 1<!-- $NetBSD: gnome.xml,v 1.12 2021/04/13 11:01:17 cirnatdan Exp $ -->
2 2
3<chapter id="gnome"> <?dbhtml filename="gnome.html"?> 3<chapter id="gnome"> <?dbhtml filename="gnome.html"?>
4<title>GNOME packaging and porting</title> 4<title>GNOME packaging and porting</title>
5 5
6<para>Quoting <ulink url="https://www.gnome.org/">GNOME's web 6<para>Quoting <ulink url="https://www.gnome.org/">GNOME's web
7site</ulink>:</para> 7site</ulink>:</para>
8 8
9<blockquote> 9<blockquote>
10 <para>The GNOME project provides two things: The GNOME desktop 10 <para>The GNOME project provides two things: The GNOME desktop
11 environment, an intuitive and attractive desktop for users, and the 11 environment, an intuitive and attractive desktop for users, and the
12 GNOME development platform, an extensive framework for building 12 GNOME development platform, an extensive framework for building
13 applications that integrate into the rest of the desktop.</para> 13 applications that integrate into the rest of the desktop.</para>
14</blockquote> 14</blockquote>
@@ -345,33 +345,33 @@ followed: @@ -345,33 +345,33 @@ followed:
345<title>Patching guidelines</title> 345<title>Patching guidelines</title>
346 346
347<para>GNOME is a very big component in pkgsrc which approaches 100 347<para>GNOME is a very big component in pkgsrc which approaches 100
348packages. Please, it is very important that you always, always, 348packages. Please, it is very important that you always, always,
349<emphasis role="strong">always</emphasis> feed back any portability 349<emphasis role="strong">always</emphasis> feed back any portability
350fixes you do to a GNOME package to the mainstream developers (see <xref 350fixes you do to a GNOME package to the mainstream developers (see <xref
351linkend="components.patches.feedback" />). This is the only way to get 351linkend="components.patches.feedback" />). This is the only way to get
352their attention on portability issues and to ensure that future versions 352their attention on portability issues and to ensure that future versions
353can be built out-of-the box on NetBSD. The less custom patches in 353can be built out-of-the box on NetBSD. The less custom patches in
354pkgsrc, the easier further updates are. Those developers in charge of 354pkgsrc, the easier further updates are. Those developers in charge of
355issuing major GNOME updates will be grateful if you do that.</para> 355issuing major GNOME updates will be grateful if you do that.</para>
356 356
357<para>The most common places to report bugs are the <ulink 357<para>The most common places to report bugs are the <ulink
358url="https://bugzilla.gnome.org/">GNOME's Bugzilla</ulink> and the <ulink 358url="https://gitlab.gnome.org/GNOME">GNOME's GitLab</ulink> and the <ulink
359url="https://bugzilla.freedesktop.org/">freedesktop.org's 359url="https://gitlab.freedesktop.org/explore/groups">freedesktop.org's
360Bugzilla</ulink>. Not all components use these to track bugs, but most 360GitLab</ulink>. Not all components use these to track bugs, but most
361of them do. Do not be short on your reports: always provide detailed 361of them do. Do not be short on your reports: always provide detailed
362explanations of the current failure, how it can be improved to achieve 362explanations of the current failure, how it can be improved to achieve
363maximum portability and, if at all possible, provide a patch against CVS 363maximum portability and, if at all possible, provide a patch against the
364head. The more verbose you are, the higher chances of your patch being 364main Git branch. The more verbose you are, the higher chances of your
365accepted.</para> 365patch being accepted.</para>
366 366
367<para>Also, please avoid using preprocessor magic to fix portability 367<para>Also, please avoid using preprocessor magic to fix portability
368issues. While the FreeBSD GNOME people are doing a great job in porting 368issues. While the FreeBSD GNOME people are doing a great job in porting
369GNOME to their operating system, the official GNOME sources are now 369GNOME to their operating system, the official GNOME sources are now
370plagued by conditionals that check for <varname>__FreeBSD__</varname> 370plagued by conditionals that check for <varname>__FreeBSD__</varname>
371and similar macros. This hurts portability. Please see our patching 371and similar macros. This hurts portability. Please see our patching
372guidelines (<xref linkend="components.patches.guidelines" />) for more 372guidelines (<xref linkend="components.patches.guidelines" />) for more
373details.</para> 373details.</para>
374 374
375</sect1> 375</sect1>
376 376
377</chapter> 377</chapter>