Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Jun 2012 07:53:52 -0400
From:      Michael Scheidell <scheidell@FreeBSD.org>
To:        <freebsd-ports@freebsd.org>
Subject:   Re: Why Are You NOT Using FreeBSD?
Message-ID:  <4FCCA1D0.6010105@FreeBSD.org>
In-Reply-To: <4FCC9DD1.7050302@ateamsystems.com>
References:  <C480320C-0CD9-4B61-8AFB-37085C820AB7@FreeBSD.org>	<1933413.9F9m1gfubp@x220.ovitrap.com>	<4FCC42BE.20101@ateamsystems.com>	<2454124.AkQPmLjFUd@x220.ovitrap.com> <4FCC9DD1.7050302@ateamsystems.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On 6/4/12 7:36 AM, Adam Strohl wrote:
> Doesn't tinderbox do this every night?
And, as a committer, here is the point.
We get reports of 'this doesn't build'.  (no fixed attached, no logs, no 
indication of what was installed first, what options taken), we try to 
get information on what happended and just get 'I am just trying to tel 
lyou its broken, and I don't have time to tell you why, its your os, you 
fix it') want a link to a recient pr where that happened?

So, we run it up in a tinderbox (for the newbie who wants this to work 
like windoes or linx , I will explain:
A tinderbox is a special virtual chrooted (jail) envirnoment. The 
tinderbox creates a blank tree, with a free copy of FreeBSD  (x), copies 
a free ports tree to it, and creates packages.
(pkg_create).  /generically/ it builds these with default options (since 
this is a batch process, that is all we can do).
If the system can fetch the source, apply the patches, compile the 
program, package it, pulls in all the necessary LIB and BUILD depends 
and then deletes the packages without leaving any leftovers, we consider 
the package fine /with default options/
This is why we ask that the luser tell us what strange things they have 
in make.conf, recommend that they update their ports tree (since we are 
running with a free ports tree), and tell us what non standard options 
were selected.

If we can't reproduce it, we can't fix it.

Many times we find that the user did not update the ports according to 
the instructions in /usr/ports/UPDATING, which, for all language ports 
(python, perl, php), involve more then just 'portmaster php-')

Once a ports tree is broken by (even a seemingly successful update), 
sometime down the road, something can and will rise up to byte[sic] you.

Give us the billions and billions of $$ MS has and the minions they have 
and maybe we can spend a year between os releases (oh, and sorry, but MS 
has no ports tree, and if a third party product doesn't work, don't even 
call them, they will charge you $300 to tell you to go back to the 
manufacturer)



-- 
Michael Scheidell, CTO
 >*| * SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FCCA1D0.6010105>