From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] nupas contrib needs rebuilding
Date: Thu, 2 Jun 2011 13:36:30 -0400 [thread overview]
Message-ID: <11a00d3743a54477fd843725e52e6d60@ladd.quanstro.net> (raw)
In-Reply-To: <20110602182636.256acb73@kolari.ethans.dre.am>
> Anyway, a little naivety has caused me more problems but I won't go
> into details. If I just grab the nupas source and mk install, will
> the end result be sane?
yes. but be careful, i'm pretty sure nupas depends on some changes
in /mail/lib. why don't you do something like this
do one install to make sure missing directories are there. ignore errors.
then
db = /n/sources/contrib/quanstro/replica/nupas/db
args = `{cat $db | awk 'int($3/10000000000) != 2 {print "-s " $1}' }
replica/pull $args nupas
- erik
next prev parent reply other threads:[~2011-06-02 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 12:56 Ethan Grammatikidis
2011-06-02 13:27 ` erik quanstrom
2011-06-02 13:57 ` erik quanstrom
2011-06-02 17:26 ` Ethan Grammatikidis
2011-06-02 17:36 ` erik quanstrom [this message]
2011-06-02 16:40 ` Yaroslav
2011-06-02 16:48 ` Federico G. Benavento
2011-06-02 17:17 ` Yaroslav
2011-06-02 17:28 ` Ethan Grammatikidis
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=11a00d3743a54477fd843725e52e6d60@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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.
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 NNTP newsgroup(s).