Created attachment 389826 [details] pidgin-telegram-9999.ebuild I managed to write an ebuild for the Pidgin plugin for Telegram: https://github.com/majn/telegram-purple Find the ebuild as attachment Regards
Created attachment 389828 [details] Manifest file Added Manifest file
Comment on attachment 389826 [details] pidgin-telegram-9999.ebuild >IUSE="" No need to set an empty IUSE. >DEPEND="sys-libs/zlib > dev-libs/openssl > dev-libs/glib:2 > net-im/pidgin" RDEPEND does need to be set. >src_compile(){ > emake all Does emake not work without a target? >src_install() { > insopts -m0755 > insinto /usr/lib64/purple-2/ > doins telegram-purple.so telegram-purple.so dolib.so <..> does not work here?
for some reason the make file does not build everything needed when just executing make (via emake). This is obviously an upstream bug in the build system. Therefore the workaround with emake all. On the other hand dolib would install into /usr/lib64/ and not into /usr/lib64/purple-2/. But this issue is likely my lack of knowledge how to use dolib correctly. einstall does also not work as expected, because the "make install" process tries to install the certificate directly into the system folder (sandbox violation). This is also one reason for the manual install (doins/dolib) statement mentioned above. PS: Somebody fixed the make file issue two days ago... https://github.com/PabloCastellano/telegram-purple/commit/89420f8ac3eb15edf4e746bd01b1f28129c02eda I do not intent to include this patch as patch file to the ebuild, because I assume that this branch will be pulled into the main development branch anyhow.
Created attachment 390070 [details] Improved ebuild respecting Jeroen Roovers comments
Created attachment 419478 [details] another telegram-purple ebuild I created the attached ebuild independently. It works apart from some non-fatal bugs. (i.e. https://github.com/majn/telegram-purple/issues/187, also I can not start secure chats) Do you experience the same issues? I have created my ebuild in the net-im category, but x11-plugin is probably more suitable. Also I don’t have chmod +x /usr/lib64/purple-2/telegram-purple.so though I have not found any difference in behaviour. Furthermore I did not include the glib dependency. Is that necessary even though pidgin already depends on it?
First ebuild (by Alan Smithee, https://bugs.gentoo.org/attachment.cgi?id=390070) failed for me with this error: >>> Compiling source in /var/tmp/portage/x11-plugins/pidgin-telegram-9999/work/pidgin-telegram-9999 ... make -j8 all /usr/bin/msgfmt -cf -o po/de_DE.mo po/de_DE.po /usr/bin/msgfmt -cf -o po/es_AR.mo po/es_AR.po /usr/bin/msgfmt -cf -o po/pl_PL.mo po/pl_PL.po tgl/Makefile.in not found. Maybe you need to 'git submodule update --init --recursive' ? Makefile:77: recipe for target 'tgl/Makefile.in' failed make: *** [tgl/Makefile.in] Error 1 make: *** Waiting for unfinished jobs.... * ERROR: x11-plugins/pidgin-telegram-9999::local failed (compile phase): * emake failed
Created attachment 458968 [details] ebuild for telegram-purple 1.3.0 as tagged in github Improved ebuild allowing for checking out specific commits related to release tags.
Created attachment 478506 [details] telegram-purple-9999.ebuild Updated ebuild for current master.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a447990a612bc157f3efddeb248c11dbe4446ba0 commit a447990a612bc157f3efddeb248c11dbe4446ba0 Author: Conrad Kostecki <conrad@kostecki.com> AuthorDate: 2018-06-19 18:26:48 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-06-20 08:21:25 +0000 x11-plugins/pidgin-telegram: New package Closes: https://bugs.gentoo.org/529908 Closes: https://github.com/gentoo/gentoo/pull/7777 Package-Manager: Portage-2.3.40, Repoman-2.3.9 x11-plugins/pidgin-telegram/Manifest | 1 + x11-plugins/pidgin-telegram/metadata.xml | 20 ++++++++++ .../pidgin-telegram/pidgin-telegram-1.3.1.ebuild | 44 ++++++++++++++++++++++ 3 files changed, 65 insertions(+)