On Fri, May 26, 2017 at 12:54 PM, Schwarz, Eric <[email protected]> wrote:
> Well, there exist different branches for Yocto which bring along different > versions of tools needed to build the stuff e.g. autotools. Obviously the > versions are not compatible as it is in the case of e.g. LaTeX (always the > same behaviour for existing features). Thus, the build behaviour changes > and there might be patches necessary which may exclude each other for > different branches. Thus, having a "krogoth" and "morty" branch for the > 0.6.0 release where just those build fixes and nothing else gets pushed on > top would make life a lot easier. Only if things build smoothly and are > easy to integrate people will use it. > If we were to extend this to every platform on which people use Cap'n Proto, we would quickly have an unmanageable number of branches -- at least dozens, maybe hundreds. I would rather have one branch that is expected to work everywhere. If different platforms require divergent code, then we need to auto-detect which behavior to use, rather than maintain separate branches. That said, you are of course welcome to maintain your own fork of Cap'n Proto where you apply fixes as needed for your environment. -Kenton -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
