From: Nils Gillmann <gillmann@infotropique.org>
To: Pierre-Antoine Rouby <contact@parouby.fr>
Cc: 31331@debbugs.gnu.org
Subject: [bug#31331] [PATCH 1/2] gnu: Add bitlbee-discord.
Date: Wed, 2 May 2018 18:41:12 +0000 [thread overview]
Message-ID: <20180502184112.fi7dtxv2lzz3rxqi@abyayala> (raw)
In-Reply-To: <20180501120535.13961-1-contact@parouby.fr>
Hi Pierre-Antoine,
this package definition is promising but needs some last tweaks.
I did not build it so far.
Pierre-Antoine Rouby transcribed 3.3K bytes:
> * gnu/packages/messaging.scm (bitlbee-discord): New variable.
> (bitlbee): Add 'install-lib' phase.
> ---
> gnu/packages/messaging.scm | 50 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 50 insertions(+)
>
> diff --git a/gnu/packages/messaging.scm b/gnu/packages/messaging.scm
> index fd1c330ce..d6bd588cb 100644
> --- a/gnu/packages/messaging.scm
> +++ b/gnu/packages/messaging.scm
> @@ -14,6 +14,7 @@
> ;;; Copyright © 2017 Theodoros Foradis <theodoros@foradis.org>
> ;;; Copyright © 2017 Rutger Helling <rhelling@mykolab.com>
> ;;; Copyright © 2018 Leo Famulari <leo@famulari.name>
> +;;; Copyright © 2018 Pierre-Antoine Rouby <contact@parouby.fr>
> ;;;
> ;;; This file is part of GNU Guix.
> ;;;
> @@ -181,6 +182,9 @@ end-to-end encryption.")
> (add-after 'install 'install-etc
> (lambda* (#:key (make-flags '()) #:allow-other-keys)
> (zero? (apply system* "make" "install-etc" make-flags))))
> + (add-after 'install-etc 'install-lib
> + (lambda* (#:key (make-flags '()) #:allow-other-keys)
> + (zero? (apply system* "make" "install-dev" make-flags))))
> (replace 'configure
> ;; bitlbee's configure script does not tolerate many of the
> ;; variable settings that Guix would pass to it.
> @@ -199,6 +203,52 @@ identi.ca and status.net).")
> (home-page "http://www.bitlbee.org/")
> (license (list license:gpl2+ license:bsd-2))))
>
> +(define-public bitlbee-discord
> + (package
> + (name "bitlbee-discord")
> + (version "0.4.1")
> + (source (origin
> + (method url-fetch)
> + (uri
> + (string-append
> + "https://github.com/sm00th/bitlbee-discord/"
> + "archive/" version ".tar.gz"))
Nitpick, I would write it like:
+ (uri
+ (string-append "https://github.com/sm00th/bitlbee-discord/"
+ "archive/" version ".tar.gz"))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> + "1bwqxlg6fwj3749y7w69n9jwsdzf5nl9xqiszbpv9k8x1422i1y1"))))
> + (build-system gnu-build-system)
> + (arguments
> + `(#:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'autogen
> + (lambda _
> + (invoke "sh" "autogen.sh")))
> + (add-before 'configure 'bash-path
> + (lambda* (#:key inputs outputs #:allow-other-keys)
> + (substitute* "configure"
> + (("\\$SHELL") (string-append (assoc-ref inputs "bash")
> + "/bin/sh")))))
Is the configure.ac in this case special, or why doesn't it pick our SHELL
that is already in the environment of the build chroot?
> + (replace 'configure
> + (lambda* (#:key inputs outputs #:allow-other-keys)
> + (invoke "./configure"
> + (string-append "--with-plugindir="
> + (assoc-ref outputs "out")
> + "/lib/bitlbee/")))))))
> + (inputs `(("glib" ,glib)))
> + (native-inputs `(("pkg-config" ,pkg-config)
> + ("autoconf" ,autoconf)
> + ("automake" ,automake)
> + ("texinfo" ,texinfo)
> + ("libtool" ,libtool)
> + ("bitlbee" ,bitlbee)
Does the buildsystem of bitlbee-discord check for bitlbee, or why is this required?
> + ("bash" ,bash)))
> + (synopsis "IRC to instant messaging gateway discord plugin")
It's a bitlbee plugin, how about:
"Discord plugin for Bitlbee"
> + (description "This package is plugin for bitlbee IRC to other messaging
> +gateway.")
You could write:
"Bitblee-discord is a plugin for Bitlbee which provides access to servers
running the Discord protocol"
I'm not very well informed about Discord, so other people might know more.
> + (home-page "http://www.bitlbee.org/")
Here we use either the homepage, and if it doesn't exist we link to
a webview of the sourcecode or its directory on an httpd where the
source is, in this case you'd use
"https://github.com/sm00th/bitlbee-discord/"
> + (license license:gpl2+)))
> +
> (define-public hexchat
> (package
> (name "hexchat")
> --
> 2.17.0
>
>
>
>
next prev parent reply other threads:[~2018-05-02 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 12:05 [bug#31331] [PATCH 1/2] gnu: Add bitlbee-discord Pierre-Antoine Rouby
2018-05-01 17:38 ` [bug#31331] [PATCH 2/2] gnu: services: bitlbee: Add plugins Pierre-Antoine Rouby
2018-05-07 9:41 ` Ludovic Courtès
2018-05-10 14:29 ` Pierre-Antoine Rouby
2018-05-10 14:37 ` Pierre-Antoine Rouby
2018-05-10 20:29 ` bug#31331: " Ludovic Courtès
2018-05-02 18:41 ` Nils Gillmann [this message]
2018-05-02 20:21 ` [bug#31331] [PATCH 1/2] gnu: Add bitlbee-discord parouby
2018-05-02 20:30 ` Nils Gillmann
2018-05-05 15:57 ` Pierre-Antoine Rouby
2018-05-07 9:49 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180502184112.fi7dtxv2lzz3rxqi@abyayala \
--to=gillmann@infotropique.org \
--cc=31331@debbugs.gnu.org \
--cc=contact@parouby.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).