On Tue, 2014-02-04 at 10:47 -0700, David Bear wrote:> I think I would like to use git to get the latest 'stable' of
samba, and
> then use success get pull on the same samba version to keep up with
> security patches added to stable. Is this a valid way to 'manage' a
> production samba instance? I doubt I would be adding 'code'. I view
using
> git as a way to get the latest stable version of samba which my current
> distribution of linux (or bsd) hasn't packaged yet. The trouble I'm
having
> is that I still think back to when I used cvs to keep current with samba
> builds and all the git instructions seem geared for those who are or will
> be developing samba code.
>
> Are there any good how-to-stay-current with production samba using git
> writeups?
The latest stable releases are always available as a tarball, otherwise
you can follow it with git by checking out the v4-1-stable branch and
doing a 'git pull' after each release of that branch.
Andrew Bartlett
--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba