Okay, going as is without the kerberos patch (but we are using MIT kerberos right? why are we using the heimdal specific stuff...) but using illumos userland throws a whole load of dependency errors at the end. What do you want to do for an oi_151a update package? Set back for oi_151a sfw-gate dependencies or ...

Christopher

On Monday, March 05, 2012 11:13 PM, Gordon Ross wrote:
Yes.  The Oracle patch set did a "shadow copy patch" (as you describe it)
by which I assume you mean the configuration strategy where they make
two copies of the source and build in each, etc.  That was done due to some
bugs in the Samba autoconf scripts, which I chose instead to fix and submit
for inclusion into Samba.  (They should be in Samba already, but were then
delayed by some copyright discussions.  Those are now resolved, so the
changes should be in samba once I update them to current samba revs.)

The change to the libraries was because I prefer linking with the normal
system default LDAP and GSSAPI support instead of the Netscape one.
Previous changes to the Samba config had switched from libldap to the
NSPR librarires due to a missing API function that Samba needs.  I fixed
our libldap in illumos to provide the missing function, so we can continue
to use the system libldap with Samba.

So in short, both of the above are just better ways to fix things than what
the Oracle userland port of samba does.

Gordon

On Mon, Mar 5, 2012 at 8:23 AM, Christopher Chan
<[email protected]>  wrote:
Hi Gordon,

In the build patch you made for illumos-userland, i notice that there are
differences from the way the current samba package on oi151a is built. Like
no more linking against sun ldap libraries, no more shadow copy patch and
some others.

is there a reason?

regards,

Christopher


On Tuesday, February 28, 2012 11:24 AM, Gordon Ross wrote:

https://www.illumos.org/projects/illumos-userland

On Mon, Feb 27, 2012 at 9:47 PM, Christopher Chan
<[email protected]>    wrote:


The patch appears to apply to a tree...which tree is it?

regards,

Christopher

_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev


_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev




_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev

_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev


_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev

Reply via email to