<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Please be patient. We'll get a snapshot, soon. A release, unclear.<br><br> - Jay<br><br><div>> Date: Fri, 24 Jan 2014 10:11:02 +0100<br>> From: adacore@marino.st<br>> To: jay.krell@cornell.edu<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] Stuck on adding new cm3 target (AMD64_DRAGONFLY)<br>> <br>> On 1/24/2014 09:45, Jay K wrote:<br>> > sorry, I'm delayed..so much to do..<br>> > I commited the networking fix..<br>> > The m3core/unix one I think we already have.<br>> > <br>> > Later...<br>> > - Jay<br>> <br>> <br>> Right, but there's no downloadable source snapshot. And if the<br>> DragonFly support isn't in there, I'll have to carry all those patches<br>> too. So my goal is to have a few patches as possible.<br>> <br>> Anyway, I have to base the port on something -- pulling latest SVN is<br>> rarely done, and CVS is never done. Some github projects don't make<br>> releases and needed to be pulled directly, but this requires first git<br>> to be built (lots of dependencies) and then github tweaks their service<br>> and everything fails. So I'm a big believer in static compressed<br>> tarballs.<br>> <br>> Which means I can't update FreeBSD cm3 version until one exists.<br>> theoretically I can package one myself, but it looks better if it's<br>> "official" and comes from one of the known m3 websites.<br>> <br>> Thanks,<br>> John<br></div> </div></body>
</html>