[Samba] Samba 3.0.26a Available for Download

[Dimitri Yioulos]

On Tuesday 11 September 2007 8:44 pm, Josh Kelley wrote:
> On 9/11/07, Ed Kasky <ed at esson.net> wrote:
> > Not being as adept at building rpm's as I could be if I had the time
> > to learn it, is there any supporting documentation anywhere that
> > describes how to go about converting from an rpm install to
> > installing from src?
> >
> > Or is it easier/preferred/better to stick with the rpm's and build
> > them from the src?
>
> I strongly prefer using RPMs on an RPM-based system; I think that
> there are a lot of advantages to letting the package manager know
> about all of the software installed on my systems.  For example, it
> lets you easily switch back and forth between a version that you build
> yourself and one that's provided by the vendor, and it lets you more
> easily install and upgrade software across multiple computers.
>
> Building RPMs yourself in this case is quite easy:
>
> Set up your RPM build environment.  Instructions are available online
> from several places;
> http://www.city-fan.org/tips/CreateRPMBuildEnvironment appears to be a
> good set of instructions.
>
> Next, download the SRPM (.src.rpm file) from the Samba site
> (http://www.samba.org/samba/ftp/Binary_Packages/Fedora/SRPMS/).
> Although the directory is labeled Fedora, it works quite well for RHEL
> and CentOS too.
>
> Finally, run "rpmbuild --rebuild samba.src.rpm".  The resulting RPMs
> will be placed in ~/rpmbuild/RPMS.
>
> Another poster mentioned sernet's RPMs.  I personally prefer to use
> the ones from Samba's web site for Fedora / RHEL / CentOS, since their
> packaging more closely matches RHEL's, but your mileage may vary.
>
> Josh Kelley
> --

Just to point out, it looks like the samba team officially blesses the sernet 
RPMs, as from the samba web site:

"http://enterprisesamba.com/  offers Samba packages for SLES, RHEL, and 
Debian."

That's good enough for me.  But, to each his/her own.

Dimitri



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.