Package Details: cog-wpe-bin 0.8.0-1

Git Clone URL: https://aur.archlinux.org/cog-wpe-bin.git (read-only, click to copy)
Package Base: cog-wpe-bin
Description: WPE launcher and webapp container
Upstream URL: https://github.com/Igalia/cog
Licenses: custom:MIT
Groups: wpe
Conflicts: cog, cog-git
Provides: cog, cog-git
Submitter: webreflection
Maintainer: webreflection
Last Packager: webreflection
Votes: 0
Popularity: 0.000000
First Submitted: 2020-10-09 05:47
Last Updated: 2020-10-09 09:13

Latest Comments

1 2 Next › Last »

webreflection commented on 2020-10-09 11:03

@caltlgin I have disowned all the trash I've previously published so that only -bin versions and older packages of mine are now under my name.

As these modules were used mostly via archibold.io site/installers I think this was the cleanest thing to do, after updating all the scripts that automatically create WPE based kiosks in Raspberry Pi and Atom SBCs.

I hope the current status is OK, as I've changed already tons of scripts to sync all these packages and their various arch at once.

webreflection commented on 2020-10-09 06:07

@caltlgin OK, I think I've made it, and yes, it's definitively better to handle packages this way ... my only concern is that I need to build in 3 platforms before being able to update one -bin but I guess that's fine. Now, I would like to actually remove old packages, and I wonder if trying to delete master branch would do it, unless I understand how to make this merge request to previous attempts. Thanks again for your help, this cleaned up a lot.

caltlgin commented on 2020-10-08 19:55

webreflection commented on 2020-10-08 19:20

@caltlgin oh gosh ... I have the feeling creating a new repo wasn't smart/good idea at all, as now I'm understanding what was the MR about, but I am not sure I can redirect now old repository to the new one ... or maybe I should remove the new one, do the merge request dance with the old one, and target it as new one next time ... damn it, can't find good documentation around this AUR behavior.

webreflection commented on 2020-10-08 18:34

@caltlgin will look for an example, as I've already published all -bin- architecture variants of cairo-glesv2-bin-$(uname -m), cairo-glesv3-bin-$(uname -m), cog-wpe-bin-$(uname -m), and wpewebkit-bin-$(uname -m) so that I might switch ASAP to the new naming convention, thanks.

caltlgin commented on 2020-10-08 18:15

@webreflection The AUR handles that. Submit Request > Merge into: ... ; Add comment

webreflection commented on 2020-10-08 16:48

@caltlgin thanks, although I will need to push packages to a new AUR repository, right? let's say I create cog-wpe-bin-x86_64 and push it in AUR, how would an MR look like to seamlessly point cog-wpe-gl-x86_64 to cog-wpe-bin-x86_64 after?

caltlgin commented on 2020-10-08 16:27

@webreflection once you have created the *-bin package; you can submit a merge request for your old package to the new *-bin package. That way the changes to the new name happen seamlessly :)

webreflection commented on 2020-10-08 16:21

@caltlgin fair enough, so I guess I should just start migrating all my wpe related packages to their bin version ... will try to figure out how to remove these one with the older name later on.

caltlgin commented on 2020-10-08 16:15

@webreflection The -bin is convention. In some cases it is enforced; eg yay, yay-bin, yay-git. Either way it helps the package users to know what they are installing.