This is the mail archive of the
mailing list for the Cygwin project.
RE: Future releases and packages
- To: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
- Subject: RE: Future releases and packages
- From: Andrew Dalgleish <andrewd at axonet dot com dot au>
- Date: Thu, 14 Oct 1999 12:03:29 +1000
> If somebody (or somebodies) would like to volunteer to do something
> this, I'll guarantee time to work with them. Until then, DJ and I
> keep plugging along.
Finding volunteers is probably the least of your problems.
I'm sure there are plenty of people (including myself) who will
volunteer to look after a sub-set of packages.
(I am already doing that internally where I work.
I'm sure there are others in the same boat.)
(warning - flame war on the event horizon :-)
What packaging system should we use?
Will the packaging system have to support all possible installation
It is possible to install cygwin in so (too?) many ways.
I use a dedicated drive letter for my root mount and a full FHS-style
Other users may want to use a sub-dir for the root, or a simpler
Then there is the text vs binary issue for scripts, etc in each package.
I'm fairly sure no current Linux package manager has to handle that. :-)
(We have to support CR-NL in case the user edits a vital file using
but we can't install text files if someone is using binary mounts.)
Should we say "We support X. If you want Y you are on your own."?
There will still be a lot of list traffic for the "Frank Sinatra"
"I did everything just like it said in the readme, except different
Of course none of these are insurmountable problems,
but they must be addressed up front.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org