Opened 15 years ago

Closed 14 years ago

#385 closed annoyingness (fixed)

archivedir vs assocfilepath

Reported by: kjdon Owned by: kjdon
Priority: low Milestone: 2.84 Release
Component: Collection Building Severity: minor
Keywords: Cc:


The perl code uses both archivedir and assocfilepath. I think these are the same thing. Can we get rid of one of them??

Change History (3)

comment:1 by kjdon, 15 years ago

This was in an email from Michael:

I'm just committing a change to this file to use "archivedir" instead of "assocfilepath" when generating the path to the Lucene text files, because this still works properly when the archives directory gets a bit weird (e.g. if you import a collection in parts and want symbolic links in "archives" to the individual archives directories). I don't think there are any disadvantages to this, and hopefully it doesn't break anything...

comment:2 by kjdon, 14 years ago

Milestone: 2.84 Release
Owner: changed from nobody to kjdon
Status: newassigned

Find out what the above message is from and make sure I haven't broken anything - in colservr c++ code??

then close the ticket.

comment:3 by kjdon, 14 years ago

Resolution: fixed
Status: assignedclosed

archivedir is still kept, used during building. but in file paths in metadata, only assocfilepath is used now.

I left lucenesource.cpp using archivedir instead of changing to assocfilepath.

Note: See TracTickets for help on using tickets.