Getting a newer version of Koha
(Koha 3.0alpha, (Gentoo) Linux 2.6.24, MySQL 5.0.56) I've seen some terms thrown around like "latest snapshot", "git" and such that seems to indicate it's possible to get a newer version of Koha than 3.0alpha. I found my way to http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=summary , but I'm not sure what to do there. Clicking on any of the links labeled "snapshot" seems to trigger a really big download, though. So, to get the latest version of Koha, should I just download the top "snapshot" link? Or is there a better way to do it? (Is there a revised release date for the beta, BTW?) Thank you.
George Adams wrote:
(Koha 3.0alpha, (Gentoo) Linux 2.6.24, MySQL 5.0.56)
I've seen some terms thrown around like "latest snapshot", "git" and such that seems to indicate it's possible to get a newer version of Koha than 3.0alpha.
I found my way to http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=summary , but I'm not sure what to do there. Clicking on any of the links labeled "snapshot" seems to trigger a really big download, though.
So, to get the latest version of Koha, should I just download the top "snapshot" link? Or is there a better way to do it?
Yes, just download the top most snapshot. I have done it a few times in the last few days. Here are few observations: 1. Download the new snapshot and extract it to a directory (gets extracted to a directory named "Koha"). 2. In that directory, follow the installation instructions. When I ran 'perl Makefile.PL, I repeated the options I gave during my original install. You might need to install an additional perl module or two -- you will given a message to that effect. 3. When you do 'make' and 'make install', it appears that only the necessary files from the new snapshot need be copied to the earlier installation of koha -- I found this to be neat! 4. Once done, you need to log in to the Koha intranet. It will update the necessary databases. Once that is done, you should be all set. If you encounter any odd problem during this, just post here. Good luck! ->HS
(Is there a revised release date for the beta, BTW?)
Thank you.
Thanks, HS. I have a number of customized templates (and even perl files) for 3.0alpha, so I guess I should: 1) backup the existing /usr/share/koha 2) backup the existing "koha" MySQL database. 3) install the snapshot into /usr/share/koha, letting it overwrite what it wants 4) copy my modified templates/files back in /usr/share koha (merging where necessary with newer Koha code). If I need to revert, I suppose I can reinstall the backed-up /usr/share/koha directory and MySQL data.
To: koha@lists.katipo.co.nz From: hs.samix@gmail.com Date: Wed, 19 Mar 2008 12:01:38 -0400 Subject: Re: [Koha] Getting a newer version of Koha
George Adams wrote:
(Koha 3.0alpha, (Gentoo) Linux 2.6.24, MySQL 5.0.56)
I've seen some terms thrown around like "latest snapshot", "git" and such that seems to indicate it's possible to get a newer version of Koha than 3.0alpha.
I found my way to http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=summary , but I'm not sure what to do there. Clicking on any of the links labeled "snapshot" seems to trigger a really big download, though.
So, to get the latest version of Koha, should I just download the top "snapshot" link? Or is there a better way to do it?
Yes, just download the top most snapshot. I have done it a few times in the last few days. Here are few observations: 1. Download the new snapshot and extract it to a directory (gets extracted to a directory named "Koha"). 2. In that directory, follow the installation instructions. When I ran 'perl Makefile.PL, I repeated the options I gave during my original install. You might need to install an additional perl module or two -- you will given a message to that effect. 3. When you do 'make' and 'make install', it appears that only the necessary files from the new snapshot need be copied to the earlier installation of koha -- I found this to be neat! 4. Once done, you need to log in to the Koha intranet. It will update the necessary databases. Once that is done, you should be all set.
If you encounter any odd problem during this, just post here.
Good luck! ->HS
(Is there a revised release date for the beta, BTW?)
Thank you.
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_________________________________________________________________ Shed those extra pounds with MSN and The Biggest Loser! http://biggestloser.msn.com/
George Adams wrote:
Thanks, HS. I have a number of customized templates (and even perl files) for 3.0alpha, so I guess I should: 1) backup the existing /usr/share/koha 2) backup the existing "koha" MySQL database. 3) install the snapshot into /usr/share/koha, letting it overwrite what it wants 4) copy my modified templates/files back in /usr/share koha (merging where necessary with newer Koha code).
If I need to revert, I suppose I can reinstall the backed-up /usr/share/koha directory and MySQL data.
Seems like a good plan. Unless your own perl scripts mess something up in the new snapshot, I don't see any problems. Please let us know how this goes. BTW, why do have modified templates? Instead, wasn't it possible to tell Koha to use your own templates instead of having to modify Koha's own? This way, you keep your templates separate from Koha's. regards, ->HS
BTW, why do have modified templates? Instead, wasn't it possible to tell Koha to use your own templates instead of having to modify Koha's own? This way, you keep your templates separate from Koha's.
To be honest, I don't/didn't know how to do that. It wasn't really a whole new template set - it was just a few tweaks to the Koha templates (for instance, to add a bottom border to each element that appears in the "Description" tab of an item in the OPAC, to separate the description from the cast from the movie rating, etc. - that sort of thing). Plus, even if I make a copy of the Koha template, I'll still have just as much work to merge my customizations and Koha's post-alpha template changes every time I download a new snapshot, so it may not make much difference... _________________________________________________________________ Helping your favorite cause is as easy as instant messaging. You IM, we give. http://im.live.com/Messenger/IM/Home/?source=text_hotmail_join
George Adams wrote:
BTW, why do have modified templates? Instead, wasn't it possible to tell Koha to use your own templates instead of having to modify Koha's own? This way, you keep your templates separate from Koha's.
To be honest, I don't/didn't know how to do that.
It wasn't really a whole new template set - it was just a few tweaks to the Koha templates (for instance, to add a bottom border to each element that appears in the "Description" tab of an item in the OPAC, to separate the description from the cast from the movie rating, etc. - that sort of thing).
Plus, even if I make a copy of the Koha template, I'll still have just as much work to merge my customizations and Koha's post-alpha template changes every time I download a new snapshot, so it may not make much difference...
Right. Thanks. regards, ->HS
George Adams <g_adams27@hotmail.com> wrote:
Plus, even if I make a copy of the Koha template, I'll still have just as much work to merge my customizations and Koha's post-alpha template changes every time I download a new snapshot, so it may not make much difference...
If someone uses git and makes changes up a branch, it might do some of the merges itself on a "git pull" type upgrade command. Record the output, though, as it will list all the files with conflicts that need resolving. Otherwise, the commands in Emacs's Tools: Merge menu might be useful, or the sdiff command-line tool (IIRC). Hope that helps, -- MJ Ray (slef) Webmaster for hire, statistician and online shop builder for a small worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237
participants (3)
-
George Adams -
H.S. -
MJ Ray