Moving basic libs to a new repo and release them as a separate package

[simo]

On Thu, 2006-02-23 at 21:26 +0100, Jelmer Vernooij wrote:
> I think more codesharing between Samba 3, Samba 4
> and other projects. However, some things that come to mind that might
> be problematic:
> 
>  - What to do about platforms that don't have libraries (shared nor
>    static)?

Distribute .a files in the devel packages.

> I guess the number of platforms that don't have either of those is so
> small these days that we could simply abort support for such
> platforms. I think Stratos VOS is probably the only one.
>    
>  - How would this change the actions a user has to perform to compile
>    Samba? Would it simply mean an extra build step?

I think we can distribute these libraries in the official tar.gz much
like we do with the documentation that come from another tree and just
have samba recognize whether it have to build the libs itself or if the
system already have them installed by means of a configure script.

> We could perhaps automate this a bit and include these libraries in
> the Samba3 and Samba4 tarballs so only developers will have to check
> them out separetely.

Exactly.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra at samba.org
http://samba.org