public inbox for
 help / color / mirror / Atom feed
From: Eray Ozkural <>
Subject: Let's start it (Re: SN backend GPL or LGPL?)
Date: Fri, 15 Feb 2002 12:26:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hash: SHA1

Hey there,

IMHO, we don't need a license different from GPL. Let it remain free...

We still have to decide on a name. I suggested sourcebase, and Mo said fuzzyp
(but that's a fuzzy name ;). It's probably going to be hosted on so we have to do an initial import to start the work. I
suggest that we start with the source/snavigator directory, with all its
contents (we don't build gui/ though). That way, we'll be forced to drop
hacked versions of tcl/tk and the old db. It's easy to use upstream tcl/tk in
the part of the code we're going to adapt. It was said on this list before
that the old berkeley db was used for performance, but is that really true?
We can go for the latest berkeley db instead of that one. It might also allow
us to use a few advanced features, those people are crazy for performance.

With that directory, we're going to have to work on the build system and do
some changes (hopefully minor) for a preliminary version. I tried the
feasibility of that and it doesn't seem hard, I've got it half-working here.

We can keep the C and tcl/tk interfaces in, and simply disable all GUI stuff.

Then, we can progress to work on the API. (Like refining library API, writing 
a C++ wrapper, an abstract database interface, etc.)


- -- 
Eray Ozkural (exa) <>
Comp. Sci. Dept., Bilkent University, Ankara
GPG public key fingerprint: 360C 852F 88B0 A745 F31B  EA0F 7C07 AE16 874D 539C
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see


  reply	other threads:[~2002-02-15 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15  9:43 SN backend GPL or LGPL? (was: SourceNav release...) Doug Fraser
2002-02-15 12:26 ` Eray Ozkural [this message]
2002-02-18 14:02   ` Let's start it (Re: SN backend GPL or LGPL?) Mo DeJong
2002-02-20  1:59     ` Eray Ozkural

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:

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

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).