Do we need the portable dependency for Vivaldi?

[NovaViper]

Hey, there's been many rapid updates that Vivaldi has been sending out lately, and the packages seem to take a really long time to get approved now, seemingly all because of the portable package dependency. I'm wondering if that dependency is necessary at all, since Vivaldi has easy to access installers and it seems like the portable package isn't updated as often as the main vivaldi package.

[NovaViper]

In particular, Vivaldi has been pushing out several security updates, and the delay in the package releases becomes a really big issue since the security patches aren't being sent out as quickly as possible (which leaves people using the package vulnerable to possible actively exploited bugs)

[bc3tech]

To conform to choco pkg naming rules, yes. .install was created to address a customer ask, which necessitated .portable and then the meta pkg. I feel your frustration doubly as I've even made a pull request to address the bug causing our delays and commented on the pkgs telling users to upvote the bug.

[iainhallam]

@bc3tech is there a new place to try to get this resolved now that the repo containing the bug has been archived?

[bc3tech]

@bc3tech is there a new place to try to get this resolved now that the repo containing the bug has been archived?

no to my knowledge. Best thing I can think to do at this point is to get on their Gitter/Slack chat and start asking questions.