Package Details: miraclecast-git 221.36be37e-2

Git Clone URL: https://aur.archlinux.org/miraclecast-git.git (read-only)
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-git
Replaces: miraclecast
Submitter: albfan
Maintainer: albfan
Last Packager: albfan
Votes: 43
Popularity: 0.783262
First Submitted: 2017-09-01 01:25
Last Updated: 2018-04-09 19:49

Latest Comments

1 2 3 Next › Last »

kuldeep commented on 2019-10-05 14:14

In build() before executing ./autogen.sh, I had to call dos2unix on multiple files (to make it compile):

build() {
  cd "$srcdir/$_name"
  dos2unix ./autogen.sh
  find . -name \*.m4|xargs dos2unix
  find . -name \*.ac|xargs dos2unix
  find . -name \*.am|xargs dos2unix
  ./autogen.sh
  ./configure --prefix=/usr --sysconfdir=/etc
  make
}

Xyne commented on 2019-08-15 12:24

The entry in the provides array should be "miraclecast", not "miraclecast-git".

albfan commented on 2018-04-09 19:51

Thanks @servimo, fixed

servimo commented on 2018-04-07 15:24

package "git-core" does not exist

albfan commented on 2017-09-01 01:27

thanks @cyrozap. I did a merge request for https://aur.archlinux.org/packages/miraclecast-git/

cyrozap commented on 2017-08-31 20:17

As rafasc mentioned, this package is currently not following the package guidelines. Typically, packages without a VCS suffix are built from tagged releases/tarballs or from a specific commit (for example, "rtmpdump"), not from git master.

I think the simplest way to solve this issue is to push the repo for this package to "miraclecast-git", add "miraclecast" to the list of package conflicts for "miraclecast-git", and then modify "miraclecast" to build from either a specific commit hash or, preferably, a tagged release/commit.

The alternative is to rename this package to "miraclecast-git". It's a more involved process, but it might result in less confusion. To rename this package (preserving votes and comments):

1. In the PKGBUILD:
a. Change `pkgname` to "miraclecast-git".
b. Add "miraclecast" to `conflicts` and `replaces` (it can be removed from `replaces` once there's an official "miraclecast" package).
2. Regenerate `.SRCINFO`.
3. Commit your changes.
4. Push to `ssh://aur@aur.archlinux.org/miraclecast-git.git`.
5. Submit a merge request at https://aur.archlinux.org/pkgbase/miraclecast/request/ to merge "miraclecast" into "miraclecast-git".

albfan commented on 2017-08-26 18:00

This package depends on master, how can it be outdated?

albfan commented on 2017-08-26 17:58

I read through https://github.com/rmarquis/pacaur/issues/567

Doesn't make sense to me that pacaur forces me to name my package. I'm trying to create the official package (and pass from AUR to ABS someday in future) so by now it depends on master, but this is the stable one.

Yaourt don't force you to follow that convention. @rafasc Do you have any link to official docs that forces that convention?

rafasc commented on 2017-03-09 00:12

when installing with pacaur:
miraclecast package(s) failed to install. Check .SRCINFO for mismatching data with PKGBUILD.

I believe this is due to:
Suffix pkgname with -cvs, -svn, -hg, -darcs, -bzr, -git etc. unless the package fetches a specific release

https://wiki.archlinux.org/index.php/VCS_package_guidelines

albfan commented on 2017-02-24 16:42

@mirco done