I tried this, but it does not look as if it takes care of such things as having a completely different perl location than the default. If what I did actually worked, there were no localized copies of the software made but rather just pointers in the httpd configuration which point back to the source location I downloaded via git. Is that what I should expect to happen? If so, and I have installed my own perl (/shared/perl/bin/perl), things are not going to work properly since all of the source code is hardcoded with /usr/bin/perl. Or is it my install which did not work properly? I find very few files copied over; and almost all are in the misc/translator directory. Thanks, Tom On 03/06/2012 04:10 PM, Chris Cormack wrote:

* Tom Hanstra (tom@nd.edu) wrote:

...

I need to explain a bit more what I'm currently trying to understand...

I can use what I've learned to compile and install the software that I pull down using git when I first pull it down.

Then, what I do is make changes which localize the software (template changes, etc.).

Now, if/when a patch comes along that I would like to make and I pull down that patch/change, what I'm not clear on is how best to move that change along to my installed version. If I fully install again, it seems that I could run the risk of overwriting something that I've localized. But I don't know of other ways in which to get the change into place.

So, I'm interested in understanding how others handle this. How does a single patch best get moved into place for testing without mucking up the localizations which have been made? When you did your install, you should have chosen dev install. This sets Koha up to run out of your git checkout.

If you didnt do this, you can manually edit your koha-conf.xml and apache config to make it run from there. That way you apply the patch in git, and now Koha is using it.

Chris

...

Thanks, Tom

On 03/05/2012 06:14 PM, Tom Hanstra wrote:

...

Is there documentation somewhere which provides some guidance on how to properly set up a clone obtained via git? I'm still learning how git works so I need some pretty basic guidance on incorporating it into my environment.

The primary questions I have are how to get the cloned version to find what it needs in a non-standard environment. For instance, I installed my own version of perl because the OS version was too old. How do I get the clone to use that?

I have learned how to set things up using the packaged versions, but would like to explore my options for setting up a clone instead. But the documentation I've seen on the Koha Wiki assumes a level of git that I have not yet achieved and/or assumes a very standard environment (as far as I can tell). So pointers on how to take the next step beyond that would be most appreciated.

Thanks, Tom

--

------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556

"Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------

_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------