The Wrapper Project
abartlet at samba.org
Wed Nov 20 12:26:10 MST 2013
On Wed, 2013-11-20 at 13:25 -0500, Simo wrote:
> On Wed, 2013-11-20 at 17:20 +0100, David Disseldorp wrote:
> > On Wed, 20 Nov 2013 14:51:13 +0100
> > David Disseldorp <ddiss at suse.de> wrote:
> > > > The wrappers are not finished yet but if you prefer to have a copy of then in
> > > > the Samba tree, I don't see a problem.
> > > >
> > > > For development, marketing and support for *other* projects it makes more
> > > > sense to have each wrapper in a separate git tree.
> > >
> > > If the projects are going to eventually live in separate repositories
> > > (I don't object), I think we should consider using git-submodules to
> > > maintain links to the appropriate git URLs and versions within the Samba
> > > tree.
> > I should clarify that this suggestion was made under the assumption that
> > the separate repositories lived on git.samba.org and were subject to the
> > same review / check-in constraints as are currently in place.
> > Otherwise it doesn't make much sense IMO.
> Why not ?
> What is so special about this code that we can't use an external
> project ? We do that for other code we have in our tree.
I've worked on and with these for quite some time now, and I am very
painfully aware how a simple, small bug in these can create bizarre and
insane to debug issues in our test code.
I therefore strongly feel that the code should be shipped in the samba
GIT tree, and should be built with our build system so that there is
absolutely now issue of version skew.
That is why I think this is a particularly special case.
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical