[fpc-devel] DragonFly BSD x86-64 support --- patch sets ready for commit to trunk

John Marino fpc-devel at marino.st
Sun Dec 7 13:22:07 CET 2014

On 11/25/2014 15:20, Marco van de Voort wrote:
> In our previous episode, Jonas Maebe said:
>>> (and
>>> not making the 2.8.0 release) so that's what is concerning me.
>> Committing large patches right before forking a stable branch is  
>> generally not done in any case (it's kind of a contraction in terms).  
>> At first sight there is nothing in your patches that can affect  
>> existing targets though, so it should be ok. Maybe remove constants  
>> that you changed to octal, just to avoid any accidental bug creeping  
>> in that way.
> Maybe we should simply branch now, and let the rest of the fpmake release
> engineering be merged back as necessary?
> That would free up trunk.

So a couple of weeks have passed.  The PR wasn't claimed.  This is a
significant contribution; not only is it a fully working target that
didn't exist before, but one that will be instantly supported through
the FreeBSD ports collection (over 100 packages).

It would be great to understand what is the plan to handle this
contribution, the associated timeline and who will be responsible for
the commit.  I'm in the process of setting up a FPC support team in
FreeBSD but obviously if no target exists for our platform, I won't have
a reason to do that.

Anyway, if somebody could provide a thoughtful update about the plan for
this DragonFly target, I would be most appreciative.


More information about the fpc-devel mailing list