[Slackbuilds-users] Corcern about sources' procedence

[Chris ABELA]

What procedure is taken in order to avoid this nightmare?
Because, knowing SlackBuild.org has a very good reputation and its
software works flawlessly most of the times, I asume you have some
method to prevent Niel and his friends from taking over Slackware
Universe.  

From: slackbuilds-users-bounces at slackbuilds.org
[mailto:slackbuilds-users-bounces at slackbuilds.org] On Behalf Of Hac Er
Sent: 09 June 2011 11:19
To: slackbuilds-users at slackbuilds.org
Subject: [Slackbuilds-users] Corcern about sources' precedence

My advise is the following:

1. If you can, audit the source code.
2. If you have a liability, prepare your Case (see 1).
3. If you cannot audit the code, then don't worry, because it is useless to
worry.

This holds for wherever the codes originates. As far as I know, the only
source code that comes with an audit report is xinetd-2.3.0.

Chris