Search Criteria
Package Details: gddccontrol 0.5.1-1
| Git Clone URL: | https://aur.archlinux.org/ddccontrol.git (read-only, click to copy) |
|---|---|
| Package Base: | ddccontrol |
| Description: | Control your monitor by software using the DDC/CI protocol (GUI) |
| Upstream URL: | https://github.com/ddccontrol/ddccontrol |
| Keywords: | cli ddc gtk monitor settings |
| Licenses: | |
| Conflicts: | |
| Submitter: | 3ED_0 |
| Maintainer: | 3ED_0 |
| Last Packager: | 3ED_0 |
| Votes: | 22 |
| Popularity: | 0.22 |
| First Submitted: | 2015-08-19 13:52 |
| Last Updated: | 2021-01-12 19:29 |
Dependencies (6)
- ddccontrol (ddccontrol-git)
- gtk2 (gtk2-patched-gdkwin-nullcheck, gtk2-ubuntu, gtk2-git, gtk2-minimal-git, gtk2-patched-filechooser-icon-view)
- autoconf (autoconf-git) (make)
- gtk2 (gtk2-patched-gdkwin-nullcheck, gtk2-ubuntu, gtk2-git, gtk2-minimal-git, gtk2-patched-filechooser-icon-view) (make)
- intltool (make)
- python (python-dbg) (make)
Latest Comments
1 2 3 4 Next › Last »
Asuranceturix commented on 2021-01-12 22:56
I'm not an expert either but, as I understand dependencies, and given that gddccontrol is merely a GUI for ddccontrol, shouldn't all dependencies (and conflicts) of ddccontrol be exclusive to the non-GUI package, so that gddccontrol only depends on ddccontrol plus whatever is needed for the GUI part? EDIT: That's exactly the case, I thought that whatever depends were specified for a subpackage were added to the general depends, but it's not like that.
Also, per your latest fix (thanks, by the way!), only gddccontrol declares a conflict with ddccontrol-git, but it stands to reason that it's ddccontrol who will want to own the same files, right?
3ED_0 commented on 2021-01-12 19:37
Sorry, looks like I don't understand how conflicts works. Package is not installed and pacman throws conflict with not installed package. Fixed.
xiretza commented on 2021-01-12 19:08
Yeah, this definitely shouldn't provide or conflict with ddccontrol-git. Managing such a conflict is the job of the -git package.
Asuranceturix commented on 2021-01-12 19:06
I can't install gddccontrol because pacman says it's in conflict with ddccontrol. If I understand correctly the PKGBUILD file, this is caused because both packages provide and conflict with ddccontrol-git, so they can't coexist, but at the same time gddccontrol depends on ddccontrol.
This appears to have been introduced a couple of commits ago: in fact I used to have them both installed with no issues. The simplest solution appears to be to move the ddccontrol-git conflicts/provides lines into the package_ddccontrol function.
janek commented on 2021-01-11 23:52
@3ED_0 thanks, I can confirm that the build is now successful.
3ED_0 commented on 2021-01-10 09:42
@jbbr: now, should works without reverting
@tmn505: done
janek commented on 2021-01-10 02:44
I always get the following error when trying to build this package since pkgrel 8 during "./configure":
Anyone else with this problem? Building on Manjaro.
Update: Build works fine when running './autogen.sh'. This issue seems to be caused by this change:
Update2: Manjaro is still on autoconf v2.69. As this was changed to fix issues with autoconf v2.70 I guess this at the same time breaks build with autoconfig <2.70
Temporary workaround for all Manjaro: Just revert the patched line & build should work fine.
tmn505 commented on 2021-01-10 02:19
Add python(python3) in makedepends, it's needed by
gdbus-codegen(https://github.com/ddccontrol/ddccontrol/blob/c662e07c0f9e064f0be5b5dad2532056b62dfdf9/src/daemon/Makefile.am#L35).xiretza commented on 2020-12-31 12:32
autoconf 2.70 runs intltoolize automatically, but without passing
--force, so the autogen.sh script no longer works. The corresponding line inprepare()can be replaced withinstead.
dlh commented on 2020-12-22 15:18
Please bump due to new release of icu