Mail Archives: cygwin/2003/04/22/01:45:08
> > using the cutting-edge in Cygwin then they'll just use the
> > net release. Could also be the birth of CPM, too.
>
> Control Program/Monitor?
Cygwin Package Manager...
> > What we'd need:
> >
> > - A CVS repository
> > - Part of the web site dedicated to the distribution
> > - A Mailing list
> > - Volunteers to handle bug reports, release updates &c
> >
> > I've put myself up, and Brian Ford raised interest.Anyone else?
>
> Well I'm interested in seeing the result :}. And I'll happily
> accept patches / even tweak the odd thing in setup to accomodate
> your needs. I can't commit the time needed to do release
> testing or policy documentation though.
>
> You'll also need a setup program to install your 'stable distribution'.
> (*)
>
> Rob
>
> (*) setup.exe can be reused, but you *will* need some changes to
> teach it that there is a stable distribution, and the unstable
> distribution. My thought on the prev / curr / test buttons has
> been to treat them like distributions, but there was a lot of
> resistance when I suggested that. So currently there is not
> separation between the three. IF there is community support,
> I'm happy to have setup present 'stable' , 'curr' and 'testing/exp'
> and have an (optionally) hard barrier between stable and curr.
...My first thought was to have a command line tool (cpm) much like the CPAN
shell, which would be easy to use and have simple commands like `install',
`update' and `remove' to modify the installation, as well as having command
line options. On second though t'would be better to have something that
could also be setup integrated.
IMO, if this does get off the ground, it would be a good start to first put
the distro together and once it's all polished then tackle the setup.exe
beast. :-)
Elfyn
--
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 -