From: Ben Martin <monkeyiq@users.sourceforge.net>
To: rhug-rhats@sources.redhat.com
Subject: Lucene & rhug & rpms
Date: Mon, 02 Feb 2004 13:23:00 -0000 [thread overview]
Message-ID: <1075728950.1352.55.camel@sam> (raw)
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hi,
Pls CC me as I'm not on the list.
Having gotton Lucene [1] to compile roughly as shown in this message
[2] I'm currently pulling down the cvs for rhug to see if lucene has
made it into rhug but not the webpages.
I notice that some of the subdirs I have currently use fluorine instead
of following the rhug-hacking [3] directions. Are there any docs on
using fluorine, or should I follow the rhug-hacking page?
BTW are the rpms/src.rpms made with the specfiles from rhug cvs
available from any website? It would be handy if I'm going to build
optional support for a gcj-ed java package to be able to point at tar.gz
+ src.rpm files for that package for folks.
As an aside, the purpose of this is that I'm looking to add optional
support for using Lucene to libferris [4] for its full text indexing
aswell as the existing native inverted file indexing support I've
created in C++.
[1] http://jakarta.apache.org/lucene/docs/index.html
[2] http://www.mail-archive.com/lucene-dev@jakarta.apache.org/msg04131.html
[3] http://sources.redhat.com/rhug/hacking-howto.html
[4] http://witme.sourceforge.net/libferris.web/
--
Blogtackular http://advogato.org/person/monkeyiq/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-02-02 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1075728950.1352.55.camel@sam \
--to=monkeyiq@users.sourceforge.net \
--cc=rhug-rhats@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).