Message-Id: <199804161208.IAA17383@elsbeth.canada.sun.com> Date: Thu, 16 Apr 1998 08:08:47 -0400 (EDT) From: David Collier-Brown <david.collier-brown@Canada.Sun.COM> Subject: Re: clientgen... To: czar@silesia.pik-net.pl
Bartlomiej Czardybon <czar@silesia.pik-net.pl>
| You can separate smblib from main samba code, but how are You going to
| keep it in state with original samba code, which is being continously changed
In at least two ways:
1) don't **really** seperate it. Ship samba and smblib updates
at the same time, and always link statically witgh it inside
samba.
2) Synchronize the two with a version number. I'm working
on a product that uses shared libraries, and we synch on
the lowest-level structures.
The latter trick predates Unix, by the way: my Multics machine
was updated regularly by routines which were sensitive to
x.y-type versions numbers. It's easy once you've done it once (:-))
--dave
-- David Collier-Brown, | Always do right. This will gratify some people 185 Ellerslie Ave., | and astonish the rest. -- Mark Twain Willowdale, Ontario | davecb@hobbes.ss.org, canada.sun.com M2N 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb