Package Details: profanity-omemo-plugin-git v0.1.1.46.ga1c77a8-3

Git Clone URL: (read-only)
Package Base: profanity-omemo-plugin-git
Description: A Python plugin to use (axolotl / Signal Protocol) encryption for the profanity XMPP messenger
Upstream URL:
Licenses: GPL3
Conflicts: profanity-omemo-plugin
Provides: profanity-omemo-plugin
Submitter: crt
Maintainer: crt
Last Packager: crt
Votes: 3
Popularity: 0.467158
First Submitted: 2018-01-25 06:46
Last Updated: 2018-04-14 19:21

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

aereaux commented on 2018-04-15 01:51

OK, I investigated installing it as a system package. Looks like the best way to do that is to do python3 install --root="$pkgdir/" --optimize=1 --skip-build instead of the current version. (It may be good to switch to python3 depends, because the profanity package is currently built with python3.) Unfortunately, right now upstream is broken when trying to do this, until something similar to this PR ( gets merged, so you may have to include a patch if you want it to work.

aereaux commented on 2018-04-12 22:21

As far as I can tell, the script doesn't take any arguments, right? In order to create a valid package, you'd need to not use that script as it always installs to the user's home directory.

crt commented on 2018-04-12 19:06

Thanks for your feedback. I don't remember where I got that argument from, but you're correct. I have updated the build to remove that argument and also corrected the pkgver().

aereaux commented on 2018-03-27 17:48

The install script doesn't have an --install_path argument. The resulting package only contains the LICENSE.

crt commented on 2018-02-12 02:59

The script in the PKGBUILD calls the needed python setup file to do the actual build of the profanity-omemo plugin. Once the build completes the same script then creates the necessary local user directory to copy over into. The license is also package() so that it gets installed to /usr/share/licenses. I guess if you really wanted you could instead just add the ./ --install_path ${pkgdir} to the build() function and leave the license install in package(), but the end result would still be the same. :)

aereaux commented on 2018-02-12 00:46

It appears that this doesn't actually package anything. The script referred to in the PKGBUILD only installs to the user's home directory. I think it should be sufficient to just install the deploy/ to the appropriate directory.