This is the mail archive of the cygwin@cygwin.com 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: setup.exe: something besides C++?


I have a question. Do contributions to setup require the same copyright
assignment as contributions to the dll? I've looked at the contributions page,
the FAQ, and the assignment form itself, and the answer doesn't appear obvious
to me. 

I have some 250+ boxes I deal with, and an unattended setup/update would be a
huge plus for me -- something I might consider contributing. I just have
serious doubts as to whether I could get my employer to agree to the copyright
assignment :-(

--Rick
--- Vince Hoffman <Vince dot Hoffman at uk dot circle dot com> wrote:
> I think here the answer is the traditional open source one, if you need/want
> it that much then go for it and code away, and if other people want like it
> then they'll join you. All the info to code something like this is available
> if you feel the need :) 
> 
> > -----Original Message-----
> > From: Steve Coleman [mailto:steve dot coleman at jhuapl dot edu]
> > Sent: 05 March 2003 15:27
> > To: cygwin at cygwin dot com
> > Subject: Re: setup.exe: something besides C++?
> > 
> > 
> > Pavel Tsekov wrote:
> > 
> > >On Wed, 5 Mar 2003, Joe Buehler wrote:
> > >
> > >  
> > >
> > >>but have any of the setup.exe
> > >>developers thought about changing setup.exe so that it is written
> > >>in something a little easier to work on, like perl/tk?  
> > >>
> > >But then, it would become _huge_. You'd have to download a 
> > bunch of other software just to install Cygwin.
> > >
> > True, It would hardly make sense to have to install Cygwin & perl/tk 
> > just to install Cygwin! (lol)
> > 
> > But then with all the recent requests for new Cygwin 
> > setup.exe features 
> > I do think there might be a use for something like the 
> > CPAN.pm package 
> > that would allow these people to script their own automatic 
> > updates or 
> > to add new custom features as required for their specific needs. No 
> > setup.exe is going to satisfy everybody, so perhaps a CYGWIN.pm ??
> > 
> > e.g.
> > %> perl ?MCYGWIN ?e ?install XFree86?
> > 
> > It wouldn't replace setup.exe since the initial install would 
> > still have 
> > to be done but it might be a good idea to have something that could 
> > check if there are updates to designated packages that are deemed 
> > important to the specific Cygwin user, and notify or even 
> > just perform 
> > the updates like the "Windows Update" service. One 
> > administrator might 
> > grab the latest packages and store them on a corporate server and all 
> > the workstations via crontab could then install from their 
> > central file 
> > server thus easing the load on all the Cygwin mirrors.
> > 
> > Steve
> > 
> > P.S. - many thanks to the Cygwin maintainers!! ;-)
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > --
> > 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/
> > 
> 
> --
> 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/
> 


--
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/


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