[Koha] Upgrade from Koha 3.00.00 to 3.0.6
Susan Mustafa
susan.mustafa at gmail.com
Mon Aug 2 17:15:03 NZST 2010
Thank you very much Chris, I believe I have a better idea of where to start
now :)
Best Regards,
On Mon, Aug 2, 2010 at 9:10 AM, Chris Cormack <chrisc at catalyst.net.nz>wrote:
> * Susan Mustafa (susan.mustafa at gmail.com) wrote:
> > Chris,
> >
> > I really am sorry to bother you with my many questions, but I would
> hope
> > that you can clarify something for me.
> >
> > At the moment, my company is using only open-source software
> applications,
> > such as OpenSIS, Koha, OpenERP, etc.
> >
> > The problem is, we got all those except Koha from Vendors [To match
> our
> > requirements/Modifications]
> >
> > To further complicate things, the company wants to keep up with the
> > updates and upgrades that source forge produces.
> >
> > How do I do all this?
> >
> > From what I understood, you are saying connect to the central git,
> > checkout a [development branch-where I can continue to make further
> > modifications to without the need to commit], and once an upgrade
> comes,
> > then I will try to MERGE my [development branch] + [central GIT].
> >
> Ideally you wouldn't need to make local modifications, and if you did
> you would do them with a system preference and then you could send
> patches upstream for inclusion into Koha.
>
> But if you want to have local changes that are never submitted upstream,
> you would clone the git repository from git.koha-community.org. Make a
> branch for your local changes, make changes, commit them to that branch,
> merge or rebase from the relevant upstream branch (in your case
> rel_3_0).
>
> Git is a distributed version control system, so you can commit locally,
> it is only when you push or send patches, that your changes move from
> being local.
>
> > Now for Koha - you are saying this is easier if I do a [Development
> > Install, rather than the recommended Production install]
> >
> If you intend to do local development, then a development install is the
> way to go. If you intend to instead just upgrade with each new release,
> then a standard install is the way to go.
>
> > Am I understanding your point, or am I way off?
> >
> > I really wish I can read some resources out there that explain how to
> do
> > client modifications to opensource projects and still be up-to-date
> with
> > whatever the central repository has. Any articles/websites would
> greatly
> > benefit me?
> >
> The best read for that is
> http://wiki.koha-community.org/wiki/Version_Control_Using_Git
> and
> http://www.myacpl.org/koha/?p=558
>
> Hope this is some help, jump onto irc sometime #koha on
> irc.katipo.co.nz, I'm around on there a bit and I can show you some
> practical examples.
>
> Better yet, if you can manage to make it to the developer conference
> part of kohacon (http://www.kohacon10.org.nz) we will be covering a lot
> about how to use git effectively.
>
> Hope this helps
>
> Chris
>
> > Best Regards,
> >
> > On Mon, Aug 2, 2010 at 8:13 AM, Chris Cormack <chrisc at catalyst.net.nz
> >
> > wrote:
> >
> > * Susan Mustafa (susan.mustafa at gmail.com) wrote:
> > > Good Day,
> > >
> > > Chris, I am using "SVN". I made my own svn repository, and not
> > using
> > > KOHA's git repository.
> >
> > Wow ... are you tracking git changes, and importing those into your
> svn
> > repo? I fear you have made a real rod for your back if not.
> > >
> > > Honestly, not sure of how to proceed.
> > >
> > > I looked at doing merging yesterday and such, but then noticed
> that
> > the
> > > final [Installed} koha, has the directory structure of
> > > intranet/opac/etc....
> > >
> > > But the freshly unzipped tar of koha 3.0.6 has many many
> different
> > > packages. So I assume I can't do merge between the two, but
> rather
> > I have
> > > to [Install KOHA 3.0.6] on a new machine THEN try and merge
> that
> > installed
> > > koha with [our installed koha]. Both then will have the same
> > > intranet/opac directory structure and merging is possible.
> > >
> > > Does that make sense? IS there is an easier way?? hehe
> > >
> > I'm not sure there is an easier way ... if you had been using git
> you
> > could checkout the rel_3_0 branch in git, and merge your local
> branch
> > into it, and run the upgrader.
> >
> > But as you have a pretty non standard Koha installation, I suspect
> yes,
> > you are going to have to do a lot of work manually merging files, I
> > strongly recommend if you are going to do local changes, that in
> future
> > you do a dev install, which runs out of your git checkout and track
> your
> > changes that way. It will make your life a million times easier when
> you
> > want to upgrade to 3.2.0
> > Chris
> > > Regards,
> > >
> > > On Mon, Aug 2, 2010 at 1:15 AM, Chris Cormack
> > <chrisc at catalyst.net.nz>
> > > wrote:
> > >
> > > * Susan Mustafa (susan.mustafa at gmail.com) wrote:
> > > > Good Day All,
> > >
> > > Hi Susan
> > > >
> > > > I would like to know how I can start the upgrade process
> > from Koha
> > > 3.00.00
> > > > to Koha 3.0.6 [Kindly keep in mind that our version of
> Koha
> > 3.0.0
> > > has a
> > > > lot of in-house changes]
> > > >
> > > How have your changes been made, have they been checked into
> a
> > local git
> > > repository?
> > > > What steps should I follow? Resources to read?
> > > >
> > > Normally you would do an upgrade as outlined in one of the
> > INSTALL
> > > files, but with local changes, its not as easy as that.
> > > > I know there is the subversion vendor branches merge
> that I
> > can do,
> > > but I
> > > > am unsure if that will work and be sufficient.
> > > >
> > > We (the koha project) don't use subversion, do you mean git?
> > >
> > > > Kindly awaiting your response,
> > > >
> > > Chris
> > >
> > > --
> > > Chris Cormack
> > > Catalyst IT Ltd.
> > > +64 4 803 2238
> > > PO Box 11-053, Manners St, Wellington 6142, New Zealand
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.10 (GNU/Linux)
> > >
> > >
> iEYEARECAAYFAkxV49wACgkQZgbcHEvgMLN2/ACdEc/x3uY0QyR6LXMEl5nUr2xa
> > > qWsAoKzJrZ8Gt4YQSMmAbrO5KKBmxM/0
> > > =pj2q
> > > -----END PGP SIGNATURE-----
> >
> > --
> > Chris Cormack
> > Catalyst IT Ltd.
> > +64 4 803 2238
> > PO Box 11-053, Manners St, Wellington 6142, New Zealand
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.10 (GNU/Linux)
> >
> > iEYEARECAAYFAkxWRdoACgkQZgbcHEvgMLMqqACgp7NdTx54KgK2hpd08EZieuyo
> > YL8AmwXPC/PkdaE65tclUrZRTuZP7dno
> > =kSxg
> > -----END PGP SIGNATURE-----
>
> --
> Chris Cormack
> Catalyst IT Ltd.
> +64 4 803 2238
> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkxWU1QACgkQZgbcHEvgMLNNWwCfWrKdW17ZEkXZEOIfYbkq6cGF
> eB8An0C0WyeeIU1hf3frVPAKWTnTvw9B
> =bHaw
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20100802/5e4a2ab0/attachment-0001.htm
More information about the Koha
mailing list