| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ApplicationIndicatorCustom.cs
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| | |
Attributes GH PR #21: https://github.com/AyatanaIndicators/libayatana-appindicator/pull/21
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
parallel (although this looks ugly).
|
|\
| |
| |
| | |
Attribute GH PR #19: https://github.com/AyatanaIndicators/libayatana-appindicator/pull/19
|
| |
| |
| |
| | |
ignoring unit tests during DEB package buids (and also fixes them).
|
|/
|
|
| |
propagating e.g. a build HOME into the DBus test environment.
|
| |
|
|
|
|
| |
this amends the dconf errors spotted lately.
|
| |
|
|
|
|
| |
their version of dh_makeclilibs.
|
|
|
|
| |
specific builds.
|
| |
|
|
|
|
| |
bindings.
|
| |
|
|
|
|
| |
python-ayatana-appindicator.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
-application Indicator should be pulled in from the desktop env's side that wants to utilize it (e.g. via the indicator-render applet).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|