Build environment for contrib

[Konstantin A. Lepikhov]

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 ;)

-- 
WBR, Konstantin	      chat with ==>ICQ: 109916175
     Lepikhov,	      speak  to ==>JID: lakostis@xxxxxxxxxx
aka L.A. Kostis       write  to ==>mailto:lakostis@xxxxxxxxxxxxxxxx

...The information is like the bank... 			  (c) EC8OR
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.trustix.org/pipermail/tsl-contrib-discuss/attachments/20050709/3ae65823/attachment.bin