This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: AdminCygwin Release


-> Larry wrote:

> Certainly this would have the potential to interfere with any existing
> Cygwin installation.

I have read that you can have more than one installation of cywgin in
a single machine...

> Also, it's not clear to me that the post-installscripts for the packages you're bundling in the MSI will be run.

Yes, I'm sure that this can be done.

>> Basically, the main idea is:
>>
>> 1- Fast installation of the package (msi). Can be also installed
>> massively via Active Directory or specialized programs.
>
>
> OK, I'll take your word that your MSI package is "better" in this
> respect.
>
>
>> 2- Fast administration of a windows machine once installed.
>
>
> Is there really a difference in usage once you've installed?  Seems to
> me there should be no difference but I don't know what the particulars are that you're thinking of.

No, no difference should be there. Once installed It will be a "normal
cygwin installation".

The idea of the release is to have a "packaged bash", so Windows
administrators can start to play on it.


>> 3- Base platform for integration with other programs, like BGINFO4X or
>> others.
>
>
> Again, it's not clear to me how the mechanism for installing Cygwin affects
> this, unless you see your MSI as growing to encompass these other programs
> as well.  If so, then your MSI has a value beyond installing Cygwin so
> that's one advantage of your approach.  I will admit, however, that I am
> no expert at building MSI installers so I can't make suggestions of
> alternative ways to structure an MSI install to leverage Cygwin installer
> and install other software as well.

Yes, this is an option: create a bundle with differnt MSIs
(AdminCygwin.MSI + BGINFO4X.msi),

Nowadays , what I do is: install MSYS + install BGINFO4X -> create BGINFO4X.msi.

What I'm trying is to substitute MSYS by CYWGIN ...

... and I thought: why don't create a "base AdminCygwin package"? I
have practically all the work done ...

So what I will try is:
create AdminCygwin.MSI -> install AdminCygwin.MSI -> install BGINFO4X
inside "AdminCygwin" -> create a new BGINFO4X.msi.

I hope that you understand me. English is not my native language.

Thanks a lot for your time.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]