all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: gnunet: Add inputs.
Date: Mon, 19 Sep 2016 15:17:33 +0000	[thread overview]
Message-ID: <874m5bzzoy.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87wpi8kkvf.fsf@elephly.net>

Ricardo Wurmus <rekado@elephly.net> writes:

> ng0 <ng0@we.make.ritual.n0.is> writes:
>
>>> Is adding “bluez” and “libogg” really needed?  They seem a little
>>> unusual for networking software.
>>
>> It is not just networking software.
>> It's been to long since I found out all these dependencies, I just
>> decided to add them to guix master now. Bluez is for bluetooth support
>> of whatever feature (look it up in either documentation or the
>> Makefile), libogg is needed for audio playback I think. I could be wrong
>> about this one. You know, the longer you work on something the more you
>> find and without comments it all gets obscure. But I really think libogg
>> in addition to libopus is for something audio related.
>
> Well, that’s why I’m asking as I don’t have time to investigate the
> reasons for the suggested changes myself.  I know what “bluez” and
> “libogg” do, but it’s a bit odd to have them as dependencies of GNUnet.

GNUnet has the ability to create an adhoc meshnetwork over bluetooth if
I remember correctly. I'll ask christian again, I never used this part.

greping gets you this:

ABOUT-NLS:157:     bluez-pin          | []             []                                |
ABOUT-NLS:341:     bluez-pin          |     [] []  []  []                [] []          |
ABOUT-NLS:525:     bluez-pin          | []  []  []                [] [] []  []    []       |
ABOUT-NLS:709:     bluez-pin          |    [] []    [] []             []              |
ABOUT-NLS:893:     bluez-pin          | []           []         []   [] []    [] []    [] |
ABOUT-NLS:1077:     bluez-pin          | []              [] [] [] []  []  []          []   | 37
src/transport/gnunet-helper-transport-bluetooth.c:100: * In bluez library, the maximum name length of a device is 8

Which is why I have to ask about this.

>
> GNUnet doesn’t encode/decode ogg audio files, does it?

It has this telephony feature (gnunet-conversation, despite the README
it no longer is experimental) and gnunet-helper-audio-record-gst
references ogg.
src/conversation/gnunet-helper-audio-record.c:41:#include <ogg/ogg.h>

configure.ac:424:# libogg
configure.ac:425:AC_CHECK_LIB(ogg, ogg_stream_flush_fill,
configure.ac:426:        [AC_CHECK_HEADERS([ogg/ogg.h],
configure.ac:428:          ogg=1
configure.ac:429:          AC_DEFINE(HAVE_OGG,1,[Have ogg]),
configure.ac:431:          ogg=0
configure.ac:432:          AC_DEFINE(HAVE_OGG,0,[lacking ogg]))],
configure.ac:434:        ogg=0)


>> If you think comments are needed because someone in the future could
>> decide to cut down the "bloat", I can comment all the dependencies with
>> which part of GNUnet needs them.
>
> Commenting unusual inputs should be enough.
>
> ~~ Ricardo
>
>

-- 
              ng0

  reply	other threads:[~2016-09-19 15:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 13:49 [PATCH 1/2] gnu: gnunet: Add inputs ng0
2016-09-16 13:49 ` [PATCH 2/2] gnu: gnunet-gtk: Add gsettings-desktop-schemas to inputs ng0
2016-09-19 13:37   ` Ricardo Wurmus
2016-09-19 15:01     ` ng0
2016-09-19 13:30 ` [PATCH 1/2] gnu: gnunet: Add inputs Ricardo Wurmus
2016-09-19 14:30   ` ng0
2016-09-19 14:46     ` Ricardo Wurmus
2016-09-19 15:17       ` ng0 [this message]
2016-09-19 15:21         ` Ricardo Wurmus
2016-09-19 15:34           ` Hartmut Goebel
2016-09-19 16:00             ` ng0
2016-09-19 15:37           ` ng0
2016-09-24 21:56           ` ng0
2016-09-19 15:04 ` ng0
2016-09-19 15:47   ` ng0

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874m5bzzoy.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.