Build environment for contrib

[Christian Haugan Toldnes]

(Jul 09 2005 13:08) Konstantin A. Lepikhov wrote:
> Hi!
> 
> I preparing some packages for contrib (osec, nginx, a few perl modules
> and gnuradius with portslave) and want clearify some question: whats
> the "right" way to build contrib packages? As I understand, it must be
> separate TSL install (now i'm using vserver) but how TSL guys evaluate
> complete build requires? Any TSL install have unique build environment
> (installed packages/config/etc) and so difficult calculate full
> requires and consider all config correlations that can be enough for
> everyone. In ALTLinux (where I maintain some packages), there are two
> programs for it - sandman and hasher
> (ftp://ftp.altlinux.org/pub/people/ldv/hasher). hasher have dependency
> to apt, sandman doesn't and good for porting to other distros like TSL
> ;) Does TSL have automated build environment and repository tracking
> tool like sandman or I may try to port sandman to TSL?  Anyway, it's
> good tool for tracking packaging bugs and separate distros creation
> and if TLS doesn't have BTE I consider look at this ;)


We don't have any such tool but handle each package manually.

The rule is that for official packages we build on a complete TSL (aka
Install everything).

Same should apply to contrib packages: Install everything from TSL, and
everything from contrib.

You decide what to link with by configuring your compilation, and add
needed build requirements.

If you find it useful, you can try to port such a tool.

c


-- 
Christian H. Toldnes
Trustix Developer