Date: Fri, 16 Dec 2016 01:17:44 +0800 From: Iblis Lin <iblis@hs.ntnu.edu.tw> To: ports@FreeBSD.org Cc: freebsd-ports@FreeBSD.org Subject: Re: The ports collection has some serious issues Message-ID: <20161215171743.GA20206@abeing> In-Reply-To: <c5bc24cc-5293-252b-ddbc-1e94a17ca3a8@openmailbox.org> References: <c5bc24cc-5293-252b-ddbc-1e94a17ca3a8@openmailbox.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I want to talk about another issue: the testing of ports framework
We usually test our ports via poudriere or synth. We have a greate ports
framework to help us build software, and we only need to write a few
lines of code to leveage it. But ... where is the testing of the framework ?
Those code under Mk/* is quite complex nowaday, and the requirement is
keeping changing (for example, more and more new languages appear,
helpers need to be added into ports framework). This will be a big barrier
for maintenance. Is time to build a next generation framework?
I think about this issue for a few weeks already, but still not get a good
answer. I only sorted out some principles and want to hear more
feedback:
1) Select a modern scripting language
Lots of testing methodology implemented in those languages.
Most of them are high-level. The cost of maintenance (hopefully)
reduce. So, I think this is a good starting point.
2) Not to abandon tons of Makfile
3) Not to introduce any new dependency for a end user
Just my imagination: In order to keep (2) and (3), I will use Python to
build a system doing Makfile code generation. The ports framework
managers and porters just write some Python function and testing code, then
generate a proper tested and stable Makefiles for users.
--
Iblis Lin
林峻頤
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161215171743.GA20206>