This is the mail archive of the
mailing list for the Cygwin project.
Re: [HEADSUP] Let's start a Cygwin 1.7 release area
On Apr 4 14:15, Corinna Vinschen wrote:
> On Apr 3 20:49, Christopher Faylor wrote:
> > [responding to the thread which started it all]
> > On Wed, Apr 02, 2008 at 02:35:51PM +0200, Corinna Vinschen wrote:
> > >- We create a ftp://cygwin.com/pub/cygwin-1.7 dir.
> > >
> > >- Under that dir, we create the full release directory structure as it
> > > exists in the parallel cygwin dir, except for the "cygwin" itself.
> > So far so good.
I'm just not sure we should really call it "cygwin-1.7". What would
be a good name, which does not refer to the actual version number?
"Cygwin" with uppercase C?
I'm volunteering to create the directory layout...
> > >- All files in the original release dir are hardlinked into their
> > > matching spot in the cygwin-1.7 dir.
> > I don't like hardlinking. It's too easy to have unintended side
> > effects. I think I'd rather just symlink the directories in the new
> > release area then rm the symlink and create a new directory when it's
> > time to populate the directory with a 1.7 version.
> In theory I agree, but it lets more room for mistakes. It's very easy
> to have a new package and just move the files to the directory, instead
> of checking if the directory is a symlink or a real dir. If the dir
> is a real dir from the start, you just dump the new package into the
> dir and remove the oldest files and be done.
> Anyway, it's nothing I really get excited about.
...using the directory symlink approach.
Could one of the setup.exe guys then create a matching setup.exe
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com