On Wed, 3 Sep 2008, Paul Jakma wrote: > The GSSAPI and LDAP support does not work on Solaris though. > > I imagine I'm not the only Alpine user who needs LDAP to access the > corporate addressbook..
Well, it hasn't bothered me not to have it, and if it is a problem, it's something we can add later. In the meantime we shouldn't let that prevent us from having Alpine. >> We merely need a way to accomplish that and use the libraries on the system >> so we don't duplicate. > > Ok, I'm not entirely familiar with IPS, but that sounds a good goal. I'm > not sure it can be achieved through upstream though (if by 'upstream' > you mean the original sources of software). Yes, what I meant was that when changes happen from upstream, say Alpine comes out with 2.01 for instance, that we can roll that back into our package so we have the latest upstream changes. What I would hope not to do is make changes to the upstream and hold them back downstream, for instance, so that we would need to apply them again once a new set of changes do in fact come from upstream. That might not be possible for all stuff, I don't know, but in the case of Alpine, the core package compiles cleanly using Studio, so we can use what comes from upstream. I'll need to look into GSSAPI and/or LDAP and see what is needed, but I compiled mine --without-tcl, as it seems that tcl is needed for Web Alpine, and that is not a deal breaker for us. >> I have always referred to the companion cd as sfw, so that is >> confusing. It has served me well, and been a good resource in the >> past. It also provided the sources, which was important to me. In that >> regard it hasn't failed me at all.:-) > > Ah, the 'CCD' (is that what it's called?). Yes. -- Alan DuBoff - Solaris x86 IHV/OEM Group
