lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: [lucy-dev] Transitioning to new namespace
Date Sat, 30 Oct 2010 00:47:45 GMT
+1 to all your suggestions below Marvin...


On 10/29/10 5:40 PM, "Marvin Humphrey" <> wrote:


If you "svn move" all directories named "KinoSearch" to "Lucy", and if you
perform a global 's/KinoSearch/Lucy/g' on the codebase, it only takes a couple
minor tweaks to get everything to build and pass all tests save one.  However,
I think we should be a little more deliberate in transitioning, moving
piecemeal when possible and examining the results for gotchas.

Starting off...

There are a number of .pm files within trunk/perl/lib which are there only as
backwards compatibility stubs.  Since everything is moving to a new namespace,
there is no point in keeping them.

I don't think there's any point in keeping the present Changes file, either.
It should have one entry, indicating the project heritage.

We'll probably end up needing the compatibility stub mechanism in the future,
though, so I'm not going to kill off the portions of perl/lib/ and
perl/buildlib/Lucy/ which support it -- just empty them out.

Marvin Humphrey

Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message