From: ng0 <contact.ng0@cryptolab.net>
To: Kei Kebreau <kei@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: Add: bbs100.
Date: Tue, 14 Feb 2017 18:16:01 +0000 [thread overview]
Message-ID: <20170214181601.b56ccwkotmqmtve3@wasp> (raw)
In-Reply-To: <87a8a5lw3s.fsf@openmailbox.org>
On 17-02-01 11:22:15, Kei Kebreau wrote:
> ng0 <ng0@libertad.pw> writes:
>
> > This patch adds bbs100. It is still maintained, the release intervals
> > are just very long.
> > It will need a service to be fully functional, but that service looks
> > like it will be small.
> > The build runs a test and does not follow 100% the INSTALL file in the
> > source of bbs100, for the reason that when you do as they recommend
> > you will sent the build system into a loop. Funny bug.
> >
> > I hope this build also terminates the "bbs" process after the check
> > phase, because when I wanted to start it I was told it already runs
> > (but I saw no bbs or its pid in my joblist).
> > The check phase says it is working, so I trust it.
>
> Can you do something about the logs showing up in the output directory?
> Perhaps reconfiguring the build so the default log directory is in
> /var/log instead of etc/log (other devs, is this okay?).
> The log contents make the build output time-dependent.
Difficult, at a short run of grep it looks as if this requires a
patch/substitute of certain occurences. I have to study this for a while
longer. I don't put this aside as a FIXME as the log directory is
probably affected at runtime (when there's a service for the bbs).
A FIXME is that the bin directory is a symlink to bin-3.3.1.
> Also, could you use a @code tag for Citadel instead of quotes since it's
> also software? Thanks!
Okay.
--
ng0 -- https://www.inventati.org/patternsinthechaos/
prev parent reply other threads:[~2017-02-14 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 15:44 Add: bbs100 ng0
2017-01-14 15:44 ` [PATCH] gnu: Add bbs100 ng0
[not found] ` <87a8a5lw3s.fsf@openmailbox.org>
2017-02-14 18:16 ` ng0 [this message]
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=20170214181601.b56ccwkotmqmtve3@wasp \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=kei@openmailbox.org \
/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).