Date: Sun, 08 Dec 1996 23:05:09 +0100 From: Andreas Klemm <andreas@klemm.gtn.com> To: ports@FreeBSD.org Cc: torstenb@pegasus.tlk.com Subject: Re: Somone working on a inn-1.5 port ? Message-ID: <199612082205.XAA04150@klemm.gtn.com> In-Reply-To: Your message of "Sun, 08 Dec 1996 21:30:47 %2B0100." <m0vWps7-000IE3C@solar.tlk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Andreas Klemm wrote: > > > > > Sorry if there should have been a discussion about that, one of the last > > > > crashes removed me from nearly all mailing lists for 2 weeks. > > > > > > I would do that, but I'm not sure if it's a good idea to upgrade it > > > before the 2.2-RELEASE is out. > > > > > > Comments ? > > > > I think the inn ports should move this way: > > > > inn -> inn-1.5 > > inn-current -> inn-unoff4 > > > > So people have a stable hacked up inn rel 1.4-unoff4 and the new inn > > to make experiments with it. > > I fully agree, but the question is: should we really upgrade the inn port > before 2.2-RELEASE is out ? > inn 1.5 is pretty new. It may have new bugs and so on. I personally see it that way: inn-unoff4 is the _stable_ inn version everybody uses. And now inn-1.5 is the _current_ version. So for everybody a version is out ... As long as there is no code freeze for the ports collection, I'd like to see inn-1.5 in the ports collection. Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<<
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612082205.XAA04150>