Date: Fri, 24 Jan 2014 18:33:33 -0500 From: Julio Merino <julio@meroh.net> To: Jilles Tjoelker <jilles@stack.nl> Cc: freebsd-testing@freebsd.org Subject: Re: [PATCH] convert /bin/sh tests over to ATF Message-ID: <CADyfeQUfxi43A4aXg%2Bdu1oGkQAjJFYH1CCXSSoaLKz8nX2hapw@mail.gmail.com> In-Reply-To: <20140124162759.GB90996@stack.nl> References: <B5290C1B-F262-479C-8D4F-A5D8B3CE5A52@gmail.com> <20140124162759.GB90996@stack.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 24, 2014 at 11:27 AM, Jilles Tjoelker <jilles@stack.nl> wrote: > > There may be some point in marking tests that are supposed to work on > any POSIX-compliant sh and ones that are inherently FreeBSD-specific, or > possibly more granular. However, this would be most useful when someone > who cares about another sh implementation works on it. That's a worthy goal, but only if the test suite was an "external component" that you shipped outside of FreeBSD and was easily applicable to other systems. As it is now, the test suite lives in the FreeBSD tree and therefore it can be considered to be FreeBSD-specific. Special-casing things out as only applying to FreeBSD will be difficult to maintain and make little sense in the current context. Now... all this can (and should) easily turn into the more generic discussion of: how to define tests that can be shared across the various BSDs and how to better maintain them? I currently have no answer for that, but it's a pretty large topic to cover. -- Julio Merino / @jmmv
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADyfeQUfxi43A4aXg%2Bdu1oGkQAjJFYH1CCXSSoaLKz8nX2hapw>