On Mon, 28 Nov 2016, Willem Jan Withagen wrote: > Hi, > > The Ceph package build config is almost ready for submission to the > FreeBSD Ports system. > Now the question is, is a copy of this also wanted in the Ceph-tree? > > Note that the FreeBSD ports are already publicly available in SVN, and > completely trackable there. > > Advantage is that all FreeBSD items are in the tree. > Disadvantage would probably be: > - There ia absolutely no way to test this > - it is not going to be used by users from the tree, but from > /usr/ports > - The version in the Ceph tree will always lagg, if only because > changes will be submitted after acceptance by the Ceph > developers. > > In my personal opinion it does have value, because it will inform > porters to other systems that there is already infrastructure for BSD. > > But the reason for asking is that I'm bivalent about this. We do this for debian and rpm distro (keep debian/ and ceph.spec in-tree), which is a bit unusual. In those cases they are the 'upstream' version of the build config, and downstream distros typically patch any additional changes they need on top. On another note, as soon as we have a working port, it would be nice to have a jenkins job that ensures that we don't break the FreeBSD build going forward... sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
