projects/package-update-indicator

view README @ 6:2477a6151087

Make PackagKit use the user's network proxies

Pick up network proxies from the user's environment and make PackagKit use
them. Setting network proxies is a privileged operation, so it is only
attempted if the user is allowed to use the polkit action
org.freedesktop.packagekit.system-network-proxy-configure without
authentication.
author Guido Berhoerster <guido+pui@berhoerster.name>
date Tue Jun 19 15:44:36 2018 +0200 (2018-06-19)
parents a4020e99e550
children d7d2ac4dbac6
line source
1 package-update-indicator
2 ========================
4 Description
5 -----------
7 The package-update-indicator utility regularly checks for software updates and
8 notifies the user about available updates using desktop notifications and
9 either a status notifier icon or a system tray icon.
11 Build Instructions
12 ------------------
14 package-update-indicator requires a POSIX:2004 compatible operating system, it
15 has been tested to work on Linux distributions. The following tools and
16 shared libraries are required to build package-update-indicator:
18 - GNU make 3.81 or later
19 - pkg-config
20 - GNU gettext 0.19 or later
21 - GNU or BSD install
22 - GLib version 2.48 or later
23 - GTK+ version 3.18 or later
24 - libappindicator 12.10.0 or later
25 - PackageKit-glib2 0.8.17 or later
26 - upower-glib 0.99.0 or later
27 - polkit 0.105 or later
28 - the xsltproc tool from libxml2
30 Before building package-update-indicator check the commented macros in the
31 Makefile for any macros you may need to override depending on the used
32 toolchain and operating system.
34 By default, all files will be installed under the "/usr/local" directory, a
35 different installation path prefix can be set via the `prefix` macro. In
36 addition, a second path prefix can be specified via the `DESTDIR` macro which
37 will be prepended to any path, incuding the `prefix` macro path prefix. In
38 contrast to `prefix`, the path specified via the `DESTDIR` macro will only be
39 prepended to paths during installation and not be used for constructing
40 internal paths.
42 The following instructions assume that `make` is GNU make, on some platforms
43 it may be installed under a different name or a non-default path. In order to
44 start the build process run `make all`. After a successful build, run `make
45 install` to install the program, any associated data files and the
46 documentation.
48 Previously built binaries, object files, generated data files and
49 documentation can be removed by running `make clean`, any additional,
50 generated files which are not removed by the `clean` target can be removed by
51 running `make clobber`.
53 Contact
54 -------
56 Please send any feedback, translations or bug reports via email to
57 <guido+pui@berhoerster.name>.
59 Bug Reports
60 -----------
62 When sending bug reports, please always mention the exact version of
63 package-update-indicator with which the issue occurs as well as the version of
64 the operating system you are using and make sure that you provide sufficient
65 information to reproduce the issue and include any input, output, any error
66 messages.
68 In case of build issues, please also specify the implementations and versions
69 of the tools and shared libraries used to build the program, in particular the
70 compiler.
72 In case of crashes, please generate a stack trace with a suitable debugger
73 such as gdb, lldb, dbx, or debug after a crash has occurred either by
74 examining the resulting core file or by running the program from the debugger
75 and attach it to the bug report. In order to generate a meaningful stack
76 trace the program as well as any dynamically linked libraries need to be built
77 with debugging information, see the documentation of the used compiler for the
78 required compiler flags. If any of the dynamically linked shared libraries do
79 not contain debugging information, please either install debugging information
80 for these libraries using mechanisms provided by your operating system or
81 rebuild the libraries accordingly. Please refer to the documentation of the
82 debugger for detailed instructions on generating backtraces.
84 License
85 -------
87 Except otherwise noted, all files are Copyright (C) 2018 Guido Berhoerster and
88 distributed under the following license terms:
90 Copyright (C) 2018 Guido Berhoerster <guido+pui@berhoerster.name>
92 Permission is hereby granted, free of charge, to any person obtaining
93 a copy of this software and associated documentation files (the
94 "Software"), to deal in the Software without restriction, including
95 without limitation the rights to use, copy, modify, merge, publish,
96 distribute, sublicense, and/or sell copies of the Software, and to
97 permit persons to whom the Software is furnished to do so, subject to
98 the following conditions:
100 The above copyright notice and this permission notice shall be included
101 in all copies or substantial portions of the Software.
103 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
104 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
105 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
106 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
107 CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
108 TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
109 SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.