Arch Linux User Repository

Automated downloading doesn't work curl: (6) Could not resolve host: Must agree to the Terms and Conditions error: failed to download Blackmagic_DeckLink_SDK_10.9.3.zip

The downloading and building process is fully automated as of version 10.8.3-2. The source file is downloaded directly from the official upstream website. Now this package currently works with AUR helpers and there is no more need for manual source file download.

To install this package, you need to download the Linux version of the Desktop Video SDK and place it next to the PKGBUILD. The desktop video SDK is available here: https://www.blackmagicdesign.com/support/family/capture-and-playback You need to enter some personal details to download it. (Hint: doesn't have to be correct)

It's done sensei

Could you please update this to 10.8? All you need to do is update the sha256sum and the version number.

@mnovick1988 Thank you for the help. You're welcome. There is already a reference to the download website in PKGBUILD file. Adding it to description could be a good idea. I understand your arguments, they really make sense. But since the download requires registration and the upstream developer doesn't provide an open and direct download link I think that it will not be a good practice to mirror the source file somewhere in the internet. If Blackmagic wanted, they could provide a direct download link, but since they don't provide, it's better to respect the download restrictions from such big company. Regarding the License, it says that the agreement is made by clicking the "AGREE" button (at developer's website). I think that it is a restriction that imposes the user to manualy download the file from developer's website in order to agree with the License. Having this restriction in mind, the source file should not be mirrored or automatic downloaded by PKGBUILD.

@bermond: i was just giving the link in refrence. While it does allow for the file:// protocol to be used, if your not providing the SDK and are not refrencing where it can be retrieved from. then this PKGBUILD is lacking the required sources to build. Please atleast put some information as to where to retrieve the sdk in the description. for people less search-savvy. It would be far easier to just download the SDK and mirror it elsewhere(the license has no limitations on mirroring/redistribution without editing.)

@Wesley_Chan Blackmagic updated the DeckLink SDK 10.5.4 zip file. It's now a smaller one and has reverted back to the simpler folder structure used until 10.5.3, without the Linux files being presented inside the directory 'CintelSDK-<version>'. I have updated the PKGBUILD to match this new zip file of version 10.5.4 with the new sha256sum. Thank you for the notice.

@Bermond I downloaded twice the file Blackmagic_DeckLink_SDK_10.5.4.zip and sha256sum is 3ccd2017c157a9deefe91365cbaabbe530fcc7cef74447238bf865cba67d6557. Could you please verify this? Edit: Oh, seems like the developers has released a new version. Lines to change: _cintelsdkver="$pkgver" sha256sums=('3ccd2017c157a9deefe91365cbaabbe530fcc7cef74447238bf865cba67d6557' cd "${srcdir}/Blackmagic DeckLink SDK ${_cintelsdkver}/Linux/include"

@mnovick1988 The link that you provided is invalid. It seems to be a kind of link that works only for a few minutes after the registration at Blackamagic's website and only to the person who registered. When trying to access it I get an expiration message: "This URL is invalid or has expired. If you are not redirected automatically, please locate your download on the Blackmagic Design Support page." As stated on PKGBUILD it's necessary to do a registration at Blackmagic's website and manually download the file. So a download link cannot be provided in the source array, but only a reference to the local file. It's up the user to download the file at Blackmagic's website and put it in the PKGBUILD folder to only after that start the makepkg process. Also, it's worth to mention that it will not work with AUR Helpers. This approach is not against the PKGBUILD rules stated in Arch Linux Wiki. Quote from the Arch Linux Wiki: "Files can also be supplied directly in the location of the PKGBUILD and added to this array. These paths are resolved relative to the directory of the PKGBUILD. Before the actual build process is started, all of the files referenced in this array will be downloaded or checked for existence, and makepkg will not proceed, if any are missing." Source: https://wiki.archlinux.org/index.php/PKGBUILD#source And I see no problems and no need to do any updates in the package() funcion. At least not now. It works nicely with me and I can build, install and use the package with no problems.