You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucy.apache.org by Marvin Humphrey <ma...@rectangular.com> on 2010/10/30 02:40:11 UTC
[lucy-dev] Transitioning to new namespace
Greets,
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/Lucy.pm and
perl/buildlib/Lucy/Redacted.pm which support it -- just empty them out.
Marvin Humphrey
Re: [lucy-dev] Transition to new namespace - *done*
Posted by Peter Karman <pe...@peknet.com>.
Marvin Humphrey wrote on 11/04/2010 10:09 AM:
> Greets,
>
> The transition to the Lucy namespace has been completed. There was still one
> monster commit at the end when classes got renamed and all the class files
> moved around -- however, it was a very straightforward changeset, because all
> of the tasks requiring judgment calls or special handling had been addressed
> with earlier commits.
>
thanks for all that work, Marvin.
--
Peter Karman . http://peknet.com/ . peter@peknet.com
[lucy-dev] Transition to new namespace - *done*
Posted by Marvin Humphrey <ma...@rectangular.com>.
Greets,
The transition to the Lucy namespace has been completed. There was still one
monster commit at the end when classes got renamed and all the class files
moved around -- however, it was a very straightforward changeset, because all
of the tasks requiring judgment calls or special handling had been addressed
with earlier commits.
Marvin Humphrey
Re: [lucy-dev] Transitioning to new namespace
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
+1 to all your suggestions below Marvin...
Cheers,
Chris
On 10/29/10 5:40 PM, "Marvin Humphrey" <ma...@rectangular.com> wrote:
Greets,
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/Lucy.pm and
perl/buildlib/Lucy/Redacted.pm 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
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++