Samba 2.2.8a no go on 4.8-Release

[Sean O'Neill]

At 04:29 PM 4/23/2003 +0100, Jan Grant wrote:
>On Wed, 23 Apr 2003, William Palfreman wrote:
>
> > On Wed, 23 Apr 2003, dick hoogendijk wrote:
> >
> > > On 23 Apr dick hoogendijk wrote:
> > >
> > > > Hmm, I don't like cups. Is it possible to *NOT* install cups but the
> > > > good old lpd (which already runs ;-) ?
> > >
> > > Oeps, bummer.. Forgot to look into the portfiles ;-)
> > > Very nice options screen. So, forget my prev msg please..
> >
> > This fixed it for me too.  I must not have had a single windows user
> > since 2.2.8a came out, and missed the original change from lpd to cups
> > by default.  It would be nice if the options screen defaulted to the
> > current settings when doing a portupgrade, or if there was an obvious
> > way of disabling it and using what setting currently exist.  The
> > brain-free option, if you like.  The problem is that I certainly don't
> > usually remember what options I set in these screens first time round,
> > when it comes to updating it six months later.
>
>I've a line much like this in my pkgtools.conf, in the MAKE_ARGS
>section:
>
>        'net/samba' => 'BATCH=yes WITH_SYSLOG=yes WITH_SSL=yes',
>
>The "BATCH=yes" suppresses the dialog.

Can someone do me a HUGE favor and let me know how they built the Samba 
2.2.8a  port ?  I'm running 2.2.7 right now.

When I tried upgrading to 2.2.8a, the make complained that my libtool is 
too old.  Well, my libtool current as of the FreeBSD ports tree - 
v1.3.  I've seen some activity on the ports mailing list that some folks 
are working on upgrading the libtool port to v1.4 which I assume is what 
Samba 2.2.8a is probably expecting.

I built subversion from scratch because of the libtool port issue but I'm 
kinda hoping to not have to do that with Samba.


--
Sean O'Neill