Re: Local repositories

On Wed, 09 Jun 2010 20:24 +0530, "Xaero" <[email protected]> wrote:
> Hi,
> 
> This is what I am really trying to achieve:
> I want to be able to upgrade to the latest version of strawberry but not
> have reinstall all the modules I have install and definitely not have
> problem with incompatible modules either.
> 
> So I thought (could be wrong) that having local::lib setup so I can
> install modules there are each time there's a new version of Strawberry I
> can download the .zip package and unzip it to C:\Strawberry\ and if
> there's any problem I can create another local::lib and install a new
> version of the modules there and if nothing works I can just delete the
> contents of C:\Strawberry\ and unzip the old version of Strawberry there.
> Wx being the main problem, it needs a lot time to install and I would
> prefer never to have to install it again.

This is true - and I need to create a par file for 5.12 one of these
minutes (5.10 ones are available)

Note that you'll have to reinstall everything when doing 5.10->5.12 or
5.12->5.14 jumps.

See the directions below.

> So the question is: llw32helper.bat is not what I want, or is it? Because
> from what I understand from the code is it sets env variables by writing
> to the registry. I would like to have something that can be changed
> easily. So it would be better to run local::lib directly is what I think.

llw32helper.bat is made so you have a "fire and forget" way to use
local::lib.

It depends on how often you feel the need to change your l::l settings
as to whether to use it.

If you want a different area for every script, it's probably a good idea
to run local::lib in your scripts, if you just want a separate area that
isn't going to be blown away on upgrades, use the helper script.

> So far so good? Is there anything that could go wrong? Is there a better
> way?
> 
> Another question I had was regarding upgrading: I use the .zip package to
> install Strawberry and set the env vars from a batch file each time I
> have to run strawberry. From what I gather the MSI installer is well
> equipped to upgrade the perl installation but what is the procedure to
> upgrade using the .zip archive?

If the second version-portion is not changing (you aren't doing a
5.10.x.x -> 5.12.x.x upgrade, for example), you can reuse your site
directory. Copy that away, blow away C:\strawberry, then extract and put
the site directory back.

If you *are* doing a second-portion upgrade, run cpan, create an
autobundle, copy that file out, blow EVERYTHING away (because you have
to reinstall XS modules in this case, anyway, and it's just easier to
install everything), then extract, and use the autobundle to reinstall.

Going *TO* the April 2010 versions, you'll need to reinstall anything
that installed a script that you want to use, because we didn't think of
separating out the site/bin directory until then. (sorry.) After the
April 2010 versions, you won't need to.

Note that in the April 2010 versions, you now have upgrade_env.bat that
adds the directories to the path for you. 

Hope this helps,

Curtis Jewell
--
Curtis Jewell               http://strawberryperl.com/
[email protected]   http://csjewell.dreamwidth.org/

Strawberry Perl for Windows betas: http://strawberryperl.com/beta/