Date: Tue, 04 May 2004 20:31:32 -0700 From: Tim Kientzle <tim@kientzle.com> To: Peter Jeremy <peter.jeremy@alcatel.com.au> Cc: Andrew.Li@alcatel.com.au Subject: Re: cvs commit: src/usr.bin/tar fts.c fts.h Message-ID: <40986014.4010507@kientzle.com> In-Reply-To: <20040504232632.GA69416@gsmx07.alcatel.com.au> References: <200405041721.i44HL22l029797@repoman.freebsd.org> <20040504232632.GA69416@gsmx07.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy wrote: > On 2004-May-04 10:21:02 -0700, Tim Kientzle <kientzle@freebsd.org> wrote: >>kientzle 2004/05/04 10:21:02 PDT >> >> FreeBSD src repository >> >> Added files: >> usr.bin/tar fts.c fts.h >> Log: >> Include local copies of fts.c and fts.h to be used ONLY on non-FreeBSD >> systems. The fts.h here is an exact copy of include/fts.h (except for >> an initial explanatory comment and the revision tags, of course). The >> fts.c here is slightly modified from lib/libc/gen/fts.c so it can >> compile correctly on non-FreeBSD systems. > > > Since a colleague of mine has just finished porting fts(3) to Tru64, Patches? > was interested in the changes you needed to make. Having looked, it > seems that your changes are primarily aimed at Linux compatibility > rather than general portability ... So far, I've heard reports from people using bsdtar/libarchive on FreeBSD 5, FreeBSD 4, and Linux. If someone sends me patches for another system, I'm happy to integrate them. <hint, hint> ;-) > Also, why wasn't this done as a repocopy? This would have made it far > easier to see the changes. Duh! My inexperienced commiter-ness is showing through again, isn't it? <sigh> Yes, this should have been a repo-copy. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40986014.4010507>