On Thu, Mar 19, 2009 at 07:06:35PM +0100, Pierre Bourgin wrote: > > On my side, I will prefer that we provide first a template mechanism or > default value in order to better use the nicely scripts provided in > install/scripts/ . > For instance, I use them but first step is to customize content of > install/scripts/ : I don't have Windows 2000 here, so what's the use to > download its related patches ? > I also have different requirements related to core installation, don't > care about app X or Y: don't want to download related files, do not want > that they appear in application/package list to deploy post-OS, and so on. > So I clean this folder content ... and have then to integrate updates > from U. project on these files: deal with which I remove, which I > patched, why the use of this particular file, etc.
It sounds like that you might have too many extra script files. How I think this is intended to be used is to only have the script files that you need in install/scripts/ on your production server. Then use the program install/tools/script-update to update the scripts with the latest version from unattended CVS. That works quite well. That way you only end up downloading files that you likely use. One thing to be careful of is that script-update will overwrite any file where there is a file with the same name in CVS. So, if you customize a file, you might want to give it a different name. Allan. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
