svn commit: r187332 - head/tools/regression/usr.bin/jot
obrien at FreeBSD.org
Mon Jan 19 08:50:32 PST 2009
On Sat, Jan 17, 2009 at 02:00:55PM +0000, Robert Watson wrote:
> On Sat, 17 Jan 2009, Stanislav Sedov wrote:
>> Was this discussed somewhere? I don't understand why we should restrict
>> our filesystem naming because of limitation of auxilary filesystems.
>> There're even more restrictive filesystems available, we couldn't support
>> them all. While previous modifications looked harmless this one seems
>> questionable to me.
>> I understand, this is a bikesched, but I really don't see a reason. You
>> can't build FreeBSD on windows anyway.
> Many of us would *very* much like to be able to cross-build FreeBSD from
> both Windows and Mac OS X, which would be highly desirable for embedded
> systems and appliance shops.
Run VMware. Seriously. Or raise a serious discussion on developers@
about this and get conciseness that cross building on MacOS X and
MS-Windows is a goal.
Juniper Networks creates VM's of FreeBSD build machines when they are
upgraded (or decommissioned) so it can build old EOL'ed JUNOS versions
if really needed on the same exact FreeBSD version as when the JUNOS
version was in full production.
If Juniper can do it - FreeBSD developers cannot?
For changes like this to be reasoned because of building FreeBSD on
Windows there should consensus. For MacOS X - there is a case sensitive FS.
> The first obstacle to making that work is
> that you can't even check out our source code correctly on those platforms,
> so fixing that is an important priority so that the remainder can be worked
See above for MacOS X users.
-- David (obrien at FreeBSD.org)
More information about the svn-src-head