Date: Tue, 4 Nov 2008 00:29:42 +0100 From: Emanuel Haupt <ehaupt@FreeBSD.org> To: "Alexander Churanov" <alexanderchuranov@gmail.com> Cc: freebsd-ports@FreeBSD.org, Emanuel Haupt <ehaupt@FreeBSD.org>, Flex <flex1980@gmail.com> Subject: Re: Boost 1.37 released! Message-ID: <20081104002942.f136adec.ehaupt@FreeBSD.org> In-Reply-To: <3cb459ed0811031506g4b450865q34d33988a688c3@mail.gmail.com> References: <20c4814a0811030712n4105c765p23983b55f729b25e@mail.gmail.com> <20081103192933.e4aeedef.ehaupt@FreeBSD.org> <3cb459ed0811031237l3adeef89t86a70030cca57fff@mail.gmail.com> <20081103223115.78fbbaef.ehaupt@FreeBSD.org> <3cb459ed0811031506g4b450865q34d33988a688c3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Emanuel, > > Copying devel/boost to devel/boost-devel sounds reasonable. > > However, I'd like to suggest moving devel/boost to devel/boost-134 and > having devel/boost updated to 1.37. For me '-devel' is always felt like > something not stable enough. Another concern is that maintaners of ports > that depend on boost would probably slow down the process of updating to > 1.37. Forking to old version contains element of intention - it's more clear > that devel/boost-134 is something out of date and temporary. This would involve much more initial work. We have many -devel ports that are actually just more recent versions. Once there is a working 1.37 port either people will start moving to 1.37, bringing the new version to each maintainers attention would help. At some point devel/boost will become 1.37 and devel/boost-devel will then either be removed or updated to a never version. Emanuel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081104002942.f136adec.ehaupt>