[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] [Help-gnunet] From IRC chat: ng0 asked me to pos
Re: [GNUnet-developers] [Help-gnunet] From IRC chat: ng0 asked me to post problems with the git docs.
Sun, 7 Oct 2018 09:19:00 +0200
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
On 10/06/2018 04:08 PM, Diagon wrote:> I've been back 3 times. I
/really/ want to try this. I do think
> this project shows a particular fragmentation of useful information,
> leaving at least one reasonably competent person, even if not a
> developer, throwing up their hands.
Thanks for the constructive feedback. I've been trying to get people to
put installation instructions into
doc/documentation/chapters/installation.texi and -only- there, but
despite this being easily editable by anyone involved, some developers
keep throwing up instructions in all kinds of places (like the github
repo Sva pointed you to, encouraging the use of non-free SaaS on top of
it!). I'm not sure what to do about this, as obviously asking people to
keep the documentation in one place or even just in one format is not
Anyway, the goal is that from installation.texi we will *generate* a Web
page (HTML, PDF), making the instructions easy to read even without
having built the documentation. You can find a _prototype_ of the new
Web page at https://stage.gnunet.org/. Once the (complex) migration is
complete, we'll make 'stage' the new main site. Sadly, there is quite a
bit to migrate (bug tracker, IRC logger, bibliography, continuous
integration, etc.), and the only person who's recently been working on
this is ng0 (thanks, ng0!).
Now, to answer some of your questions:
> Also, he had libcurl4-gnutls-dev. Is that a replacement for
Yes, if available, it can be used as an alternative.
> He has no optional packages either, but included a few not
> mentioned in that README: zlib1g-dev
This is for compression. Very, very commonly available.
This is very, very optional and new for pre66.
Very common, used somewhere in the gettext context.
> miniupnpc, which of course makes me curios what these are for.
Optional, for UPnP-support, a protocol to tell your NAT to open external
I hope this helps a bit where we are and where I hope to go! As usual,
help would be welcome.
Description: OpenPGP digital signature
|[Prev in Thread]
||[Next in Thread]|
- Re: [GNUnet-developers] [Help-gnunet] From IRC chat: ng0 asked me to post problems with the git docs.,
Christian Grothoff <=