luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-09-12 21:36:14 +02:00
Code Issues Packages Projects Releases Wiki Activity
Low-level core library that forms the basis for projects such as GTK+ and GNOME.
27,706 Commits 295 Branches 574 Tags 110 MiB
C 95.4%
Python 2.4%
Meson 1.3%
Objective-C 0.3%
Shell 0.2%
Other 0.4%
61075ef0bd
Go to file
Michael Catanzaro 61075ef0bd Expand security policy to cover previous stable branch 
The goal here is to reconcile the difference between GLib's 6-month
security policy and GNOME's 12-month policy (which may soon be expanded
to 13 months, gnome-build-meta#731). It's strange for GLib to be an
exception when the rest of GNOME supports two stable branches at a time.
I'm not aware of any other GNOME project with a shorter release lifetime
than GNOME itself, and it results in a situation where the previous
stable version of the GNOME runtime never receives any GLib updates,
since we stick with the same GLib version for the entire release and do
not do security backports.

But I also want to avoid creating an expectation that GLib maintainers
will do a bunch of additional backporting work, so most commits should
be out of scope. We can say maintainer discretion will be used to
determine whether a backport to the previous stable branch is warranted.
And normally, it won't be, so the goal should be no previous stable
branch releases. But occasionally we might feel a CVE is important
enough that a release really is warranted.
2023-10-03 09:12:37 +01:00
.gitlab-ci ci: Use meson compile rather than bare ninja 2023-08-16 13:07:05 +01:00
.reuse docs: Add licensing/copyright data to GVariant specification 2022-11-08 15:46:16 +00:00
docs gio: Rename GTK_USE_PORTAL to GIO_USE_PORTALS 2023-10-02 15:00:23 +01:00
fuzzing Add fuzzing harness for g_utf8_normalize() 2023-04-14 15:50:47 +00:00
gio Merge branch '3107-use-portal' into 'main' 2023-10-02 17:27:36 +00:00
glib tests/gutils-user-database: Fix test on macOS 2023-09-27 16:19:44 +02:00
gmodule Revert "build/gmodule-2.0.pc: Move compiler flags from Libs to Cflags" 2023-07-18 18:26:49 +01:00
gobject Add value annotation to G_TYPE_FUNDAMENTAL_MAX 2023-10-02 01:29:50 +01:00
gthread meson: Add tests for generated pkg-config files 2023-04-17 14:25:52 +02:00
LICENSES Add a SPDX LicenseRef for the license historically used for tests 2022-11-02 12:34:19 +00:00
m4macros m4macros: drop unused m4 files 2023-07-30 17:03:07 +04:00
po Update Turkish translation 2023-10-01 18:29:58 +00:00
subprojects meson: Don't accidentally pick up intl fallback in the first test 2022-12-31 05:13:10 +05:30
tests Convert tests/assert-msg-test* to glib/tests/assert-msg-test* 2022-06-28 11:19:21 +01:00
tools tools: Add script to create UAC manifests for Windows 2023-06-30 11:32:44 +08:00
.clang-format CI: Code check formating in CI 2019-11-21 14:03:01 -06:00
.dir-locals.el Add .dir-locals.el to tell Emacs users not to use tabs for C 2012-07-30 04:09:08 -04:00
.editorconfig docs: Add .editorconfig file 2021-10-28 14:47:53 +01:00
.gitignore docs: Move INSTALL.in to INSTALL.md 2022-05-11 13:02:49 +01:00
.gitlab-ci.yml ci: Use meson compile rather than bare ninja 2023-08-16 13:07:05 +01:00
.gitmodules ci: Update git paths to reflect new GitLab URI 2022-11-02 16:49:51 +00:00
.lcovrc build: Move lcovrc file to root so it’s picked up by Meson 2022-04-28 11:57:45 +01:00
CODE_OF_CONDUCT.md docs: Add a code of conduct document 2022-05-11 12:30:58 +01:00
CONTRIBUTING.md ci: Use meson compile rather than bare ninja 2023-08-16 13:07:05 +01:00
COPYING docs: Add all used licenses in a REUSE-compatible directory 2022-05-17 17:23:34 +01:00
glib.doap Rename GTK+ to GTK (mostly comments and documentation) 2023-05-10 10:56:44 +07:00
INSTALL.md docs: Document issue and merge request triaging and review guidelines 2023-06-29 16:50:00 +01:00
meson_options.txt build: Add runtime_dir option to set runstatedir path 2022-12-02 21:48:03 +00:00
meson.build meson: Fix Windows build with PCRE2 as sibling subproject 2023-10-01 23:06:49 -05:00
NEWS 2.78.0 2023-09-08 14:42:18 +01:00
README.md Expand security policy to cover previous stable branch 2023-10-03 09:12:37 +01:00
SECURITY.md Expand security policy to cover previous stable branch 2023-10-03 09:12:37 +01:00

README.md

GLib

GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.

The official download locations are: https://download.gnome.org/sources/glib

The official web site is: https://www.gtk.org/

Installation

See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows.

Supported versions

Upstream GLib only supports the most recent stable release series, the previous stable release series, and the current development release series. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.

See SECURITY.md for more details.

Documentation

API documentation is available online for GLib for the:

Discussion

If you have a question about how to use GLib, seek help on GNOME’s Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib.

Reporting bugs

Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.

Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.

In bug reports please include:

  • Information about your system. For instance:
    • What operating system and version
    • For Linux, what version of the C library
    • And anything else you think is relevant.
  • How to reproduce the bug.
    • If you can reproduce it with one of the test programs that are built in the tests/ subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
  • If the bug was a crash, the exact text that was printed out when the crash occurred.
  • Further information such as stack traces may be useful, but is not necessary.

Contributing to GLib

Please follow the contribution guide to know how to start contributing to GLib.

Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):

Closes: #123

Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.