Skip to content

New App: V2ray Plugin

mahc9kez requested to merge mahc9kez/fdroiddata:v2ray-plugin into master
  • The app complies with the inclusion criteria
  • The original app author has been notified (and supports the inclusion)
  • All related fdroiddata and RFP issues have been referenced in this merge request
  • The upstream app source code repo contains the app metadata (summary/description/images/changelog/etc) in a Fastlane or Triple-T folder structure
  • Builds with fdroid build
  • Releases are tagged

V2ray Plugin is a SIP003 plugin based on V2ray for Shadowsocks-android.

The source code of the Android app is released under GPL-3.0, the JNI library v2ray-plugin is used as git module and licensed under MIT.

Someone else opened an issue in the app repo before, asked about add this app in F-Droid.

I have opened an pull request on upstream for adding metadata. The metadata in upstream has been merged into master branch but not include in any tagged release yet, just /metadata/ in the F-Droid output metadata folder structure (similar to fastlane).

and I have added Summary and Description to the build metadata, it's just a plugin and does not have a home activity, I think it's fine even if the app repo does not have metadata. The app also not translated other language on Google Play, only have two screenshots and changelogs in addition.

I have tested it builds with fdroid build on macOS, but not really sure if golang or jdk version could cause problems on debian.

Currently summary and description included included in build metadata, upstream had merged /metadata/ in master branch, if everything works as expect, the next tagged release will include the metadata from app source repo. (and then we can remove the summary and description in the build metadata)

Edited by mahc9kez

Merge request reports