[Pkg-samba-maint] Early plans for a merged samba3/samba4 package

[Christian PERRIER]

Here's a first summary of discussions we had, here at "Barcamp" after
SambaXP 2012 (we==Ivo de Decker, Luk Claes, Jelmer Vernooij and me).

As Samba upstream is now merging samba 3 and samba 4, we need to merge
our own packages.

Given that what's currently called "samba 4" is meant to provide
everything currently provided in "samba 3", the general idea is to
converge towards one single package named "samba".

The version number of that package will be 2:4.x.y (keeping the epoch
introduced by my past errors!).

The new package will provide all binary packages currently provided by
samba and samba4 packages. The only overlap is smbclient. According to
Jelmer, smbclient should be built from source3 anyway as smbclient
from source4 will be discarded.

So, the new package will indeed be "binaries from current
samba4"+"binaries from  current samba".

The merge should be initiated preferrably after the release of
wheezy. Current samba4 and samba can still live their lives until
wheezy is release, the way they are done right now.


The only action will be, at one point of time to upload a "samba"
package that is indeed samba4 building the samba3 binaries. As this
package will provide all binaries currently provided by samba4, the
samba4 package should then be "semi-automatically" removed (according
to Luk).

Bugs reported against the binary packages (the vast majority) can then
continue to live their lives. The only ones we'll have to take care of
manually are those reported against the samba4 *source* package,
deciding that either they only belong to the "oldstyle" samba4 or they
also affect the new samba source package.


Waiting for your comments and additions. I hope I summarize things
well.

Next action (aha) will be to decide *where* to maintain all this. I'm
not sure we can continue to survive with subversion but is anyone
ready to try playing with svn->git?
(I'd personnally favor git, which I tend to be more comfortable with
as I have to use it more for other stuf....and also because upstream
uses git anyway and, yes, I know we did setup a bzr repository..:-))

Given that our current Subversion is kinda clumsy (/me being the
culprit for most of the clumsyness, I'm afraid), do you guys thinks it
is really possible to convert it as it has so many tags and branches
(and subprojects, some of which being quite dead).

-- 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20120511/d8941372/attachment.pgp>