-
-
Notifications
You must be signed in to change notification settings - Fork 203
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e700650
commit 94a4a84
Showing
3 changed files
with
6 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
94a4a84There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@InfernoZeus @scowalt @NGMarmaduke
Thanks as always for updating! 👍👍👍
Is there any chance that this can be automated? The release is now being published by TravisCI and the deploy config could be improved by automatically updating the AUR package(s) and the cask package. I'm not sure about choco, though. Unless it runs under wine, there's no possibility for it to be automatically updated, since travis doesn't have a Windows env. Appveyor as another CI could be added, but this would need to be synced between Travis and I don't know if that's possible.
Please also see #331: The project's name is going to be changed soon...
Thanks a lot!
94a4a84There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chocolatey package information incoming.
Would love your thoughts on this! Uploading 0.16.0 now.
94a4a84There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So choco can be run by using mono and powershell on Linux, but there are no choco and powershell packages in any Ubuntu repos/PPAs available. The required mono packages are whitelisted on TravisCI and the Powershell .deb package can be downloaded from their Github releases page.
How do you get around the
Cannot find type [System.Net.WebClient]errors when trying to install choco? (similar to https://gitter.im/PowerShell/PowerShell?at=57b9eff887f779f069166908)Wouldn't it make more sense setting up Appveyor as an additional CI service and build/push to chocolatey from there? The sync issues I was talking about do only exist if the package is downloading from the github releases page.
Right. The livestreamer dependency could be removed completely if there's a streamlink package, I'd say. I don't know if a choco package for streamlink is already being worked on, but if you're interested in helping setting this up, you could ask for the current status on the streamlink repo.
Is there a way in chocolatey to set a "replaces" property, like in PKGBUILD on Arch? If not, having a simple "proxy-package" with a dependency of the new package is good enough.
94a4a84There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR open: Homebrew/homebrew-cask#25571 - will take a look at automation this week
94a4a84There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Arch's package has been updated to 0.16.0.
Re Streamlink: it looks like someone has already set up a streamlink AUR package, so moving over to that should be easy.
Re name change: I think the procedure for AUR is to create a new package with the new name, and then request a merge of the old one into that. This should carry over any comments and votes from the old package.
Re automation: The current steps I take to update the AUR package are change the version number in PKGBUILD, and then run
updpkgsumsandmakepkg --printsrcinfo > .SRCINFO(these tools are both provided by thepacmanpackage, which is a 'default' package on Arch). We could replace both of those with a couple of md5sums and seds, for basic updates at least. Pushing the change to AUR is a git commit & push - not sure how best to handle that part.94a4a84There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@InfernoZeus
Updating the AUR package should be really simple. It's basically just cloning the repo, sed-ing both PKGBUILD and .SRCINFO (makepkg is ofc not available on Travis (Ubuntu 14.04), although https://git.archlinux.org/pacman.git/tree/scripts could be used), committing the changes and pushing them. The required SSH key can be stored as a encrypted config var or as an env var.
I'll create a new AUR account so you can add it as a co-maintainer once I've finished writing the bash script.
Edit:
The checksums in the PKGBUILD could be updated to sha256 instead of md5, so the ones of the checksums.txt can be used without hashing the files again in a weaker hash algorithm.