Mail Archives: cygwin/2008/06/21/13:44:02
Ralph Hempel a écrit :
> cuicui wrote:
>
>> You need to modify the "setup.ini" file, create "virtual" (empty)
>> package that belongs to the "Base" category and make all the additional
>> packages you want dependant of this virtual package by filling the
>> "requires" field.
>
> Ok, so how do you keep the setup.ini from being downloaded every time
> you connect to the server?
Mmm, I'm not sure there's an overlay mechanism, in my case I basically
append the "virtual" package text at the end of the setup.ini everytime
I collect a fresh package list.
> My plan is to have a c:\cygwinSetup directory on my local server,
> where I have the latest and greatest packages I need, and then
> on each machine (usually vmware machines) that I need to install on,
> I have a possibly different set of needs besides Base.
>
> So one set of scripts grabs all the packages we need to the server, and
> the other set of scripts builds the cygwin installation on the local
> machines. This reduces the overall load on the mirrors.
>
> I guess I'm actually implementing a local mirror for the packages, now
> that I think about it. Is there a way to limit the scope of the packages
> that I choose to mirror locally?
Maintaining a mirror simply consists in keeping the installation files
in one place and sticking to a mirror for more convenience (otherwise a
new directory named by the mirror URL is created in the repository).
The setup scopes the packages by itself as far as it's only downloading
the packages you choose to install (+ the "base" packages).
Regards,
Nicolas
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -