Search Criteria
Package Details: miraclecast-git 326.f3debd5-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/miraclecast-git.git (read-only, click to copy) |
---|---|
Package Base: | miraclecast-git |
Description: | MiracleCast provides software to connect external monitors to your system via Wifi. It is compatible to Miracast. Link-management works, everything else is still being worked on. Replaces openwfd. Contribute on https://github.com/albfan/aur-miraclecast |
Upstream URL: | https://github.com/albfan/miraclecast |
Licenses: | GPL |
Conflicts: | miraclecast |
Provides: | miraclecast |
Submitter: | albfan |
Maintainer: | albfan |
Last Packager: | albfan |
Votes: | 58 |
Popularity: | 0.70 |
First Submitted: | 2017-09-01 01:25 (UTC) |
Last Updated: | 2023-02-15 11:50 (UTC) |
Dependencies (4)
- git (git-gitAUR, git-glAUR)
- glib2 (glib2-selinuxAUR, glib2-patched-thumbnailerAUR, glib2-gitAUR)
- python3 (python)
- systemd (systemd-selinuxAUR, systemd-gitAUR)
Latest Comments
« First ‹ Previous 1 2 3 4 Next › Last »
Xyne commented on 2021-11-19 11:52 (UTC) (edited on 2021-11-19 11:53 (UTC) by Xyne)
The "provides" array is a way to indicate to pacman which additional dependencies a package can satisfy. It should never contain $pkgname because it is already implicit that all packages satisfy dependencies on themselves. In the case of VCS packages, you should include the package name without the VCS suffix ("miraclecast" in this case) because the VCS package is normally functionally equivalent to the non-VCS version for dependency resolution. In general, for "foo-git", "provides=(foo)" and "conflicts=(foo)" mean that "foo-git" can be used in place of "foo" but not alongside it, usually due to conflicting files.
The "replaces" array should also be removed. That is reserved for packages that supersede other packages (e.g. for name changes). VCS packages provide alternatives, but they do not supersede their non-VCS counterparts.
This has always been our policy. You do not need to remove the $_name variable. It's common practice to define it and then use it throughout the PKGBUILD. Please see my suggestion below.
As for the package version, it should be updated automatically when you build the package due to the pkgver function. Whenever that's updated, you can reset the pkgrel to 1. The only time you would need to bump the pkgrel is if you update the PKGBUILD without changing the pkgver, which may happen if upstream is not very active.
albfan commented on 2021-11-19 11:29 (UTC)
I was explicitly told to provide a vcs package and provide miraclecast-git that do conflict with a possible miraclecast from releases. Is the policy changing?
If I remove the $name I will have to remove that on build all steps too right? Why is that needed?
Should I set package version as 1 always for a vcs package?
Marzal commented on 2021-11-18 19:13 (UTC)
From https://wiki.archlinux.org/title/Arch_User_Repository
https://archlinux.org/groups/x86_64/base-devel/
js-on commented on 2021-11-18 13:25 (UTC) (edited on 2021-11-18 13:26 (UTC) by js-on)
Was not able to install
aur/miraclecast-git 221.36be37e-2
on the fly on 5.13.19-2-MANJARO #1 SMP PREEMPT Sun Sep 19 21:31:53 UTC 2021 x86_64 GNU/Linux.autoreconf
from packageautoconf
andaclocal
from packageautomake
were missing. May add it to the requirements?eNV25 commented on 2021-08-19 11:30 (UTC)
diff with the necessary changes:
kuldeep commented on 2019-10-05 14:14 (UTC) (edited on 2019-10-05 14:14 (UTC) by kuldeep)
In build() before executing ./autogen.sh, I had to call dos2unix on multiple files (to make it compile):
Xyne commented on 2019-08-15 12:24 (UTC)
The entry in the provides array should be "miraclecast", not "miraclecast-git".
albfan commented on 2018-04-09 19:51 (UTC)
Thanks @servimo, fixed
servimo commented on 2018-04-07 15:24 (UTC) (edited on 2018-04-07 15:33 (UTC) by servimo)
package "git-core" does not exist
« First ‹ Previous 1 2 3 4 Next › Last »