This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: How to simplify cygwin+perl application deployment
- From: "Gerrit P. Haase" <freeweb at nyckelpiga dot de>
- To: "Hsu, Yung-Kao (Yung)" <ykhsu at lucent dot com>
- Cc: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Wed, 12 Jun 2002 17:13:42 +0200
- Subject: Re: How to simplify cygwin+perl application deployment
- Organization: Esse keine toten Tiere
- References: <275654F2AE237D438ACC1FE2697CD8C91C8542@nj7460exch008u.ho.lucent.com>
- Reply-to: "Gerrit P. Haase" <freeweb at nyckelpiga dot de>
Yung-Kao schrieb:
> Expat & XML::Parser alone costed me a few hours after some patches :-(
I'm on the way contributing expat right now. With my binary of expat
XML::Parser builds OOTB without errors?
Soon I will load up a second 'release' of expat-1.95.3.
http://koeln.convey.de/cywgin/expat/
watch out for expat-1.95.3-2-src.tar.bz2 and expat-1.95.3-2.tar.bz2
> My question is whether it is possible to archive one such installation
> and unpack it in another machine? If so, what are the issues that we
> need to be aware of? Thank for any input.
Sure, you can build as many modules as you need and make a package of
perl including all the modules. Should be also no problem to bundle
single modules for individual setup.
Gerrit
--
=^..^=
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/