Re: [Lxr-dev] Status of this project?

[Maximilian W. <ma...@rf...>]

Am Thursday, den 22 March hub Paul Smith folgendes in die Tasten:

> On Thu, 2007-03-22 at 16:24 +0100, Jan-Benedict Glaw wrote:

> > That said, I think we should have a view at the documentation again.
> > After that, lets release v1.0 and focus on the new goodies afterwards.

> That sounds fine, but maybe a 0.9.5 release for people to test before
> 1.0?

I think that´s a good idea.

> > > I´ve a yet unfinished patch to push the version and arch lists
> > > in drop-down boxes but this breaks the diff function IIRC.

> > I think this should be v1.1 material.

> Agree.

More time to hack on it :)

> > The speed-up patches posted could probably make it into v1.0, though.

> The second version of the patch, that doesn't require changes to
> LXR::Files, I think is a good candidate.  It's a simple algorithmic
> change that only impacts genxref and clearly makes sense, and helps a
> lot when dealing with swish-e and trees with binary files.

Sound good.

> > There's also the exit() compatibility patch for perl5. I think this
> > should also go in before v1.0 is pushed out.

> Critical to get in, IMO, are the enhancements to allow the code to work
> with MySQL 5 (the quoting of `release` so it's not considered a
> keyword).  A number of the bugs and patches on the Savannah site all
> deal with this single issue.

Would it be problem to quote it every time?

> There needs to be some cleanup in this as well; note that the lxr.conf
> file allows you to rename the database and table prefix, which is
> great... but there's no way to CREATE those databases/tables with
> different names other than editing the initdb-* file by hand, which is
> not so great.

> Maybe the initdb-* files need to become Perl scripts, which can read
> lxr.conf and make the appropriate substitutions.  Then the invocation
> model could change to something like:

> 	./initdb-mysql | mysql
> 	./initdb-postgres | psql

I guess these scripts would need the 'baseurl' as parameter to get the
correct data from lxr.conf?

The use case would be to have several project databases indexed by lxr
side by side in the same database but with different table
prefixes/names?

I´m not that sure if this is really needed, maybe others have some
experiences about that?

> (not sure for Oracle).  I can look into that if people think it's a good
> idea.

Sound like an interesting approach.

Ciao
Max
-- 
	Follow the white penguin.