Arch Linux User Repository

@frol Seems like you forgot to update .SRCINFO

@frol Actually, it would probably be best to keep it so it still conflicts with this owl-git package which doesn't provide owl.

@frol If a new owl-git package provides owl (which it should), it's redundant to conflict with owl-git as it would be covered by the conflict with owl (though it doesn't hurt to leave it in)

@0x9fff00 I have created owlink-git package, submitted a merge request (it is pending; I should only wait for someone else to accept the request, right?), sent a PR to the upstream fixing the references. It seems that I only left with the last step, that is I should remove owl-git from provides, but I don't think I should drop it from the conflicts as /usr/bin/owl will, most certainly, get into conflict there.

Here's what I believe is the correct process:

1. Create a new package owlink-git with the following changes (I also added git to makedepends as it's required for downloading the sources):

diff --git a/PKGBUILD b/PKGBUILD
index 8a21537..f712288 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,6 +1,6 @@
 # Maintainer: Vlad Frolov <frolvlad@gmail.com>

-pkgname=owl-git
+pkgname=owlink-git
 pkgver=0.0.0
 pkgrel=1
 pkgdesc='An open Apple Wireless Direct Link (AWDL) implementation written in C'
@@ -8,7 +8,9 @@ arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
 url=https://owlink.org/
 license=('GPL3')
 depends=('libpcap' 'libev' 'libnl')
-makedepends=('cmake')
+makedepends=('cmake' 'git')
+provides=('owlink' 'owl-git')
+conflicts=('owlink' 'owl' 'owl-git')
 source=(
   "$pkgname::git+https://github.com/seemoo-lab/owl.git#branch=master"
   "git+https://github.com/google/googletest.git"

2. Submit a merge request to merge owl-git into owlink-git
3. Change all references to owl-git (in the opendrop/opendrop-git packages and in the installation instructions on GitHub) to owlink-git
4. Remove owl-git from provides and conflicts so a new owl-git package can be created as a VCS version of owl

@0x9fff00 This package is a VCS version of owl project (https://github.com/seemoo-lab/owl), so this is just a regular naming collision. Do you happen to know how to gracefully handle the package renaming? Should I remove this one (disown?) and create a new one?

This package should be renamed to owlink-git (or something similar) as the current name implies that it's the VCS version of the owl package, which is a different program. It should also provide owlink and conflict with owl (since it also includes the file /usr/bin/owl).